ormlite-servicestack

ServiceStack ORMLite is great, I've typically steered clear of the ORM mentality preferring to build databases as it makes sense to build databases instead of a 1:1 class model. That said, there are a couple of things that I seem to be running into difficulty around, I'm certain it's simply my ignorance shining through. First: Is there a way to manage multiple result sets using ORMLite? I know that one can use the QueryMultiple method using Dapper, but for whatever reason I'm having a bear of a time figuring out how to use the built-in Dapper implementation of ServiceStack. Second: Is there a

For a table that has an identity: [AutoIncrement] public int Id { get; set;} When inserting a new row into the database, what is the best way to retrieve the Id of the object? For example: db.Insert<> (new User()); The value of the Id is 0 after the insert, but in the database this obviously is not the case. The only possibility I can see is the following: Id = (int)db.GetLastInsertId(); However I don't believe this would be a safe call to make. If there are 100's of inserts happening at the same time, an Id for another insert may be returned. In EF when you do an insert the Id is set for you.

So, mythz didnt like my no-so-scientific benchmark question in a previous SO question, but since I would like to switch over to OrmLite, I need to figure out if it is slow, and if so, why. In my "research", I come to the conclusio that complex objects, that in OrmLite are blobbed to JSON, is the culprit of very slow SELECTs. Therefore, I created a new project that focuses solely on OrmLite, and does not compare with anything else other than itself, and the aim here is to see the differences between having blobbed JSON objects, and not having them. It can be found on GitHub: https://github.com

I selected ServiceStack OrmLite for my project which is a pure Data-Oriented application. I am willing to allow the end user to create his own Object Types defined in an XML format that will be used to generate classes at runtime using CodeDOM . I will be also defining some "system" objects required by the application (i.e. User ) but I cannot foresee all the properties the end user will use and therefore I am looking for a way to allow extending the classes I create in design time. Sample bellow public class User { public Guid Uid { get; set; } public String Username { get; set; } public

ServiceStack has delivered on EVERYTHING I've thrown at it, except the SAAS (Multi-tenant) use case where single API instance is using several databases of the same schema, one per tenant. These databases, because of legal reasons need to be housed in separate instances. So, my question is this, "Is it possible to change the connection per Request based on meta from a filter? My question is somewhat similar to this one , but with the added twist that each database is the same. Thank you, Stephen Edit: If memory serves me correctly I think mythz and I have discussed this before and found that

I've been checking ServiceStack's documentation, but I haven't found a way to do many to many relationships with ServiceStack.OrmLite, is it supported? Is there a workaround (without writing raw sql)? I'd like to have something like this: Article <- ArticleToTag -> Tag Thanks!! It's not implicitly handled automatically for you behind the scenes if that's what you mean? But as OrmLite is just a thin wrapper around ADO.NET interfaces anything is possible. In OrmLite , by default every POCO maps 1:1 with a table. So if you wanted the table layout you would create it just as it looks in your