ormlite | An ORM in Rust for developers that love SQL | SQL Database library

The API Key AuthProvider may not suit your use-case as it's designed to generate API Keys for registered users to provide an alternative way for them to call protected APIs.

To be able to model this using ServiceStack's built-in Auth API Key Auth Providers I would still have a registered AuthProvider and users representing the client that would use the API Keys.

But instead of providing User registration functionality, add them into the database manually then Generating API Keys for Existing Users.

You'll need to configure your preferred RDBMS to store the API Keys and Users in:

This issue should be resolved from the latest v6.0.3 pre-release that's now available on MyGet.

If you have an existing ServiceStack v6.0.3 installed you'll need to clear your NuGet packages cache to update to the latest version, e.g:

By default JsonStringSerializer uses ServiceStack.Text Typed JSON Serializer which can't deserialize an object back to its original type since that type information is lost, all it sees is the runtime object Type which it leaves as a string since it doesn't know what other object it should deserialize to.

Which is why it's recommended that you serialize typed DTOs so the type information is preserved, e.g:

A single column value can't possibly have two values at the same time.

What you want is either:

Anytime you see a missing type or missing method exceptions when using the MyGet pre-release packages it means you have a dirty installation (i.e. using pre-release packages from different build times).

In which case you'd need to Clear your Nuget packages cache and download the latest packages again, which ensures all your packages are from the latest same build:

OrmLite has to check if the record exists before it decides whether a db.Save* should either insert or update the record. This leaves room for the possibility that if 2 requests tried to concurrently save the same new record at the same there could be a race condition should the first insert occur just after the second requests check.

Typically this is the result of a double posting bug firing off 2+ concurrent requests. Changing it to use explicit db.Insert* and db.Update* wont help since you'll get the same response with 2+ inserts.

The proper way to handle this is to use the native upsert functionality in each RDBMS which OrmLite doesn't support yet, please vote for the feature request to get notified when the feature is implemented.

I just figured it out.

When I imported ormlite-core and ormlite-jdbc, I imported different versions of them. I changed it in my maven POM to where it is the same version and that corrected the issue!

This is what I changed my maven POM dependencies to:

Returning JSON functions is the same as returning an additional string column. Since you can't mix Tuples with both Table Type and scalar values you would need another way to access the additional string value.

You could use parse the custom results as a dynamic result set, accessing all columns individually, but in this case you could create a custom result class with the additional string column and a helper to return the typed results, e.g:

I've just added a GetAllTables() API in this commit which returns the primary and joined tables added in an SqlExpression.

This is available in the latest ServiceStack v5.11.1+ that's now available on MyGet.