As AutoCrud and AutoQuery are just regular ServiceStack Services everything you’re used to that works with normal services should just work in AutoCrud as well.
As Request Filters have implementation coupling (e.g. dep to ServiceStack.dll) they need to be annotated on your Service implementation class, so to use the [CacheResponse] attribute you’ll need to annotate them on Service classes containing the AutoQuery Services.
The [CacheResponse] attribute only caches side-effect-free GET or HEAD requests so they’re going to ignore AutoCrud’s destructive Post/Put/Patch/Delete requests, but otherwise it would’ve been applied like any other filter.
But the [ConnectionInfo] and [NamedConnection] multi-db attributes (and general multitenancy support) work as normal, as seen in the tests added in this commit.
To recap the [ConnectionInfo] Request Filter attribute is added to the Service implementation class which for AutoCrud Services would look like:
[ConnectionInfo(NamedConnection = AutoQueryAppHost.SqlServerNamedConnection)]
public class AutoCrudConnectionInfoServices : Service
{
public IAutoQueryDb AutoQuery { get; set; }
public Task<object> Any(CreateConnectionInfoRockstar request) =>
AutoQuery.CreateAsync(request, Request);
public Task<object> Any(UpdateConnectionInfoRockstar request) =>
AutoQuery.UpdateAsync(request, Request);
}
And the [NamedConnection] attribute is annotated only on the DB Model, i.e. not on the Request DTOs, e.g:
[NamedConnection("SqlServer")]
public class NamedRockstar : Rockstar { } //DB Model
// AutoCrud Services:
public class CreateNamedRockstar : RockstarBase,
ICreateDb<NamedRockstar>, IReturn<RockstarWithIdAndResultResponse>
{
public int Id { get; set; }
}
public class UpdateNamedRockstar : RockstarBase,
IUpdateDb<NamedRockstar>, IReturn<RockstarWithIdAndResultResponse>
{
public int Id { get; set; }
}
For consistency in the latest v5.8.1 now on MyGet I’ve renamed the AutoCrud Services to include the *Async suffix convention, so the generic CRUD Methods on IAutoQueryDb are now:
public interface IAutoCrudDb
{
/// Inserts new entry into Table
Task<object> CreateAsync<Table>(ICreateDb<Table> dto, IRequest req);
/// Updates entry into Table
Task<object> UpdateAsync<Table>(IUpdateDb<Table> dto, IRequest req);
/// Partially Updates entry into Table (Uses OrmLite UpdateNonDefaults)
Task<object> PatchAsync<Table>(IPatchDb<Table> dto, IRequest req);
/// Deletes entry from Table
Task<object> DeleteAsync<Table>(IDeleteDb<Table> dto, IRequest req);
/// Inserts or Updates entry into Table
Task<object> SaveAsync<Table>(ISaveDb<Table> dto, IRequest req);
}
because this way if i’m not mistaken and understood it correctly hi could build a control panel where i dynamically decide which permission/role are required for a service.
Thanks again for you patience is working now.