CustomFieldAttribute's Order property is breaking "The Field Ordering"

seems need stand-alone-attibute for Order property

ServiceStack.OrmLite/src/ServiceStack.OrmLite/OrmLiteConfigExtensions.cs
internal static ModelDefinition GetModelDefinition ( this Type modelType ) { ...
if ( customFieldAttr != null ) order = customFieldAttr.Order;
... }

public f11 {get;set}
public f2 {get;set}

[CustomField ("VarChar(1234") ] public MsgField {get;set}

public f31 {get;set}

[CustomField (Order(3) ] public f32 {get;set}

public f45 {get;set}

Add operators IF, ELSE, EXISTS, MERGE, INSERT OR UPDATE

https://keydb.dev/

KeyDB is a Faster, Drop-In Alternative to Redis

KeyDB maintains full compatibility with Redis modules, API and protocol.
Seamlessly drop in KeyDB and maintain full compatibility with your existing clients, scripts and configurations.

I assume because KeyDb is billed as a "drop-in" replacement that this would be low hanging fruit to get ServiceStack.Redis to support Redis-KeyDb

support cockroach db for GenerateCrudServices

right now, you cannot import postman metadata exposed by SS into the latest version of Postman because its complaining about v1 schema and conversion requires an insane amount of npm garbage to be installed.

any chance of adding v2 postman metadata, or links to v1 and 2?

Redis supports a certificate-based authentication scheme as well as the legacy password and more recent user + password schemes. Cloud providers such as RedisLabs as well as self-hosted and Docker-based Redis servers also support this method of authentication.

This should be added to ServiceStack so the full range of authentication schemes are supported.

Thanks.

Allow a signal to be passed in when making requests via the client side lib servicestack-client.

https://davidwalsh.name/cancel-fetch

For example, if you use MQ message, consider supporting dapr.

SS supports deserializing nested request objects if they are sent in URL as JSV. The typescript client should support this when sending a request object that has a nested object. At the moment it just appends the word "Object" to URL. I think if it doesn't support it then it should generate an error/warning when detecting a nested object as would save some confusion.

Implement support for Redis 5.0+ Streams, as described here:

https://redis.io/topics/streams-intro

redis 6.0.6 supports ACL. ACL is powerfull and secure, which user can write, which user can only read. What wildcard keys can be read...
Current version of ServiceStack allows password but not a specified username.
AUTH password -> AUTH username password

Is this something that could be done? Would bring powerful streaming to ServiceStack

This would be super helpful to have the current Aurelia template updated with the authentication piece that has been added to the angular and react spa templates.

It would be very useful to have the implementation of .net core IDistribuitedCache interface on ServiceStack caching providers. This would improve the integration with other modules that support the standard .net cache interface.

References:
https://docs.microsoft.com/en-us/aspnet/core/performance/caching/distributed?view=aspnetcore-3.1
https://docs.microsoft.com/en-us/aspnet/core/performance/caching/distributed?view=aspnetcore-3.1

Currently the PostgreSQL text match operator @@ throws validation error when used in a Ormlite custom query string.

Would be nice to get support for that and also support for parameterised query to support tsquery type.

Could we add a .Net Core version of ServiceStack.Caching.Memcached? The derived library has been updated here

https://github.com/enyim/Memcached2