Support of HStores when using Dictionary<string,string> or as a new field attribute.

HStores (key values) are very good in certain scenarios (logging/auditing) and complex parsing is easier to do in .NET than in SQL.

Custom SQL that SELECT's data is easy, but not easy to insert/save hstore in custom sql.

Also Npgsql already supports them.

More info here:
https://forums.servicestack.net/t/cannot-insert-idictionary-string-string-into-hstore-column/6894

Trying to UpdateOnly, when onlyField is typed as SqlExpression and the query has a Join an error will be thrown that says "The multi-part identifier "DepartmentJobCode.DepartmentId" could not be bound."

Example:
var jobsQuery = _db.From<dev.ScheduleEvent>()
.Join<dev.DepartmentJobCode>((se,jc)=> se.Job == jc.JobTitleId)
.Where<dev.DepartmentJobCode>(e => Sql.In(e.DepartmentId, departments))
.Update(x => new { x.Published, x.ModifiedBy});
db.UpdateOnly(new dev.ScheduleEvent { Published = false, ModifiedBy = userId}, onlyFields: jobsQuery);

1h
https://aws.amazon.com/blogs/aws/new-amazon-dynamodb-transactions/

Add Transactions to IPocoDynamo

When an error occurs processing a batch of requests, the responses for the successful requests are lost. It would be helpful if these successful response are returned along with the error that stopped further processing.

Templates has a sendToGateway option. In a Web App it would be good if settings could be provided for the baseUrl for the ServiceStack service which should receive the request.

Extend https://github.com/WBPuge/ServiceStack.OrmLite/blob/master/src/ServiceStack.OrmLite/Expressions/Sql.cs
to support following sql math operators:
Sign
Abs
Floor
Ceil/Ceiling
Round(x, y)

For a few of us, we are constrained with having to use mongodb or other nosql databases instead of an RDBMS.

It would be good if we have a some sort of native mongodb support or at least a few examples/patterns of how to go about a full mongodb/servicestack solution. I understand that we have examples of redis usage but, we do not have authentication and other similar aspects as examples.

Love the tooling still! yet hate to work with anything else now (you spoiled us!) that I have to work with mongodb.

Cheers!
-Simo

The only thing that keeps me from dropping CsvHelper and using SS Csv capabilities for everything is that quite often I need a custom type converter.

For instance sometimes currency is a mix of numbers and letters or there can be inconsistent data.

If there was a way to register a method that would receive the raw column values and alter them then this would make it much more versatile in my opinion.

AWS Charges by the IOp, not supporting UPSERT effectively doubles the cost (and reduces the performance) of running mysql/mariadb on that platform with the SELECT/INSERT behavior of OrmLite

See issue: https://forums.servicestack.net/t/should-csv-respect-dto-datamember-order-value/1799

Help Pluralsight update their videos on Servicestack and/or show how to update their example solutions to the latest version of Servicestack.
Another alternative is to offer an updated version of the videos example code localy (somewhere at servicestack.net/github.com).

I tried to do a update to the latest versions myself and I ran into loads of problems. To the extent that i gave up.

At present, the AspNetWindowsAuthentication is not supported in .NET Core. ASP.NET Core does allow for Windows Authentication (through IIS reverse proxy), so it would be great to have support for this in ServiceStack.

I made an attempt at porting it myself, and it kind of works, though I'm sure I'm missing some subtleties on how it works, as I sometimes get "header already set" errors on some requests. In case this never gets picked up, here's a gist of my attempt:

https://gist.github.com/darkonejr/7bcdcf7aea9fee7d21329fd58de5d43d

Support change MaxLimit of query feature for specific dto

The NativeTypesFeature is used by ServiceStackVS does a great job of looking at all types exposed by Services. However, it fails to include (or exclude via options) any type only referenced via a "ReferencesAttribute" data annotation. This forces me to either create a complete clone of the type just for automatic client DTO generation, or to create an additional dummy service route that exposes this type.

Can the NativeTypesFeature be enhanced to also include Reference(TYPE) and/or References(TYPE)?

We have an application that always return an AppContentResponse<T>. AppContentResponse contains some properties that are present in every response of every method we have, while the T is the actually Type of the response.

When we look at the metadata documentation, ServiceStack generates the documentation for AppContentResponse<T> without also documenting T. The strange thing is that if I create a class that actually implements AppContentResponse<TypeOfThatResponse>, both types get automatically documented.

I filed an issue at https://forums.servicestack.net/t/expand-generic-type-when-documenting-responses/5676 if you are looking for more details.

While some methods of SqlExpression<T> supports up to 15 generic parameters (Where, And, Or) others like Select, SelectDistinct and GroupBy only supports a couple. When building complex queries, it's easy to select data from more than 7 tables, or group by fields from more than 4 tables.

Could you implement more Select, SelectDistinct and GroupBy overloads like you did for Where, And and Or?

There is no specific number of parameters needed, but I think that the default 15 is a good start.

I didn't find support of client side sharding with sentinels in your Redis API. It will be a nice to have feature. I asked this question on stackoverflow, if you have some solution for the problem, it would be great to hear: https://stackoverflow.com/questions/50107173/servicestack-redis-is-sharding-supported-in-sentinel-mode

The generated code does not conform to company rules so I get a bunch of useless warnings when I run code analysis on my solution.

Just adding a

// <auto-generated>
// This code was generated by ServiceStack.
// </auto-generated>

block above or below the /* Options: */ block would be enough to exclude the generated file from code analysis.

The Redis client supports distributed locks, which is a really useful feature, the same is possible using DynamoDB.

Reference Implementation:
https://github.com/awslabs/dynamodb-lock-client