I just realized, I could probably just use the underlying Dapper functionality… so I tried:
var results = db.Query<FileTbl>("select * from [FileTbl] where FileId in @FileIds ", new { FileIds = fileIds });
But I got hit with an error I have seen before (using Dapper in a WebApi project for a client):
System.InvalidOperationException: 'Error parsing column 5 (RowVersion=System.Byte[] - Object)'
I checked that old project, and I have a note that for Dapper and EF, the RowVersion has to be declared differently to how OrmLite requires. From Dapper-based project (where I’d hoped to use SS but wasnt able to), I have note to myself:
//[CustomField("RowVersion")] // We wanted to make ServiceStack.Ormlite write out the column creation as
RowVersion/Timestamp, but Dapper/EF needs it to be a byte[]
public byte[] RowVersion { get; set; }
Any ideas on whether its possible to make the Dapper Byte[] concept play nice with SS Ormlite? Ie. If i declre my rowversions using SS conventions, but somehow make the Dapper QUERY call respect that format?
Otherwise, I am going to have to build up a lot of Where In conditions for this project manually, and really wanted to avoid that…
(its 3am, and I have to shelf this for now, to be continued tomorrow), but thanks.