Is it implicitly handled automatically for you backstage if that is what you mean? But since OrmLite is just a thin shell around ADO.NET interfaces, anything is possible.
In OrmLite, by default, each POCO table maps 1: 1 to a table. Therefore, if you want the table layout to create it in the same way as in your database, for example
var article = new Article { ... }; var tag = new Tag { ... }; var articleTag = new ArticleTag { ArticleId = article.Id, TagId = tag.Id }; db.Insert(article, tag, articleTag);
Although you might want to use the built-in blobbing in OrmLite, where any complex type is simply serialized and stored in a single text field. So you can do something like:
var article = { new Article { Tags = { "A","B","C" } };
Where Tags is just a List<string> , and OrmLite will take care of transparently serializing it into the database field for you.
source share