You can bump up that “stale time” if you have long running transactions in your system that make it look like it’s stale
Marten should be putting tombstone events in place of the failed events, but maybe we've never tested that workflow in the case of serialization failures earlier in the SaveChanges() call.
Im using System.text.json + https://github.com/Tarmil/FSharp.SystemTextJson and I actually like it. It gives some errors as kind of expected but actually now I have a model that I am happy with. I.e. strings are now not nullable but need to be "string option" (FsharpOption) and null will error on de/serializing
To balance that, F# user experience will be my next goal after merging Upcasters PR. If you could write up all of your challenges in the GH issue, then I could try to include that.
Still, I need to learn F# language and idiomatic approach better, so it’ll take some time
It's not something that always happens and I haven't been able to reliably recreate it, but ive taken to putting an extra ToString on all my header calls
JObject could be returned if there was an unknown type and it did dynamic deserialisation. It can be cast to the specific type.
Tested with Newtonsoft and fsharp types are serialized okish, however the deserialization format for options and discriminated unions is imho not ideal. For both types are different json representations possible, Ill try write a blogpost about my experiences but not yet sure when...
Do you think that being able to do custom serialization like in my PR would help? JasperFx/marten#2314
2 replies
In theory, it’s more for event schema migration, but I was thinking of making it more generic also for documents as the next step
What is the default for
AutoCreateSchemaObjects if it's not specified? I have queries periodically failing for a service running in Google Cloud Run with timeouts like so. Just wondering what could be the reason.---> System.TimeoutException: The operation has timed out.
at Weasel.Core.Migrations.TimedLock.Lock(TimeSpan timeout)
at Weasel.Core.Migrations.DatabaseBase`1.generateOrUpdateFeature(Type featureType, IFeatureSchema feature, CancellationToken token)
at Weasel.Core.Migrations.DatabaseBase`1.ensureStorageExists(IList`1 types, Type featureType, CancellationToken token)
at Marten.Linq.MartenLinqQueryProvider.ensureStorageExistsAsync(LinqHandlerBuilder builder, CancellationToken cancellationToken)
at Marten.Linq.MartenLinqQueryProvider.ExecuteAsync[TResult](Expression expression, CancellationToken token)
My assumption is that the default is
None, but why is it then trying to apply migrations
@EgorPavlikhin_twitter It's
CreateOrUpdate to enable quick developer starts. Check out this topic maybe: https://martendb.io/configuration/optimized_artifact_workflow.html
The only implication is that patching documents won't work
@grzybsonssg No, the method call parser business is only used for Where() clauses -- but feel free to open an issue for some kind of extension for this. I think we've added an
OrderBy() overload extension method that lets you feed in raw SQL. That might be easier than mucking with Linq.
Or, easiest, make a read-only getter property that calculates that value and it'll get serialized into the JSON and you'll be able to order or search on that at will. Kinda like building an index for that expression
@pnjakste Here's a rundown of the functionality that won't exist w/o PLv8: https://martendb.io/documents/plv8.html.
@phillip-haydon The compiled query class itself just defines the SQL and the “plan” to get results out of the SQL. To run a compiled query asynchronously, it’s just this method: https://github.com/JasperFx/marten/blob/master/src/Marten/IQuerySession.cs#L204
Use this parent class: https://github.com/JasperFx/marten/blob/master/src/Marten/Linq/ICompiledQuery.cs#L38. Then pass that into
IQuerySession.QueryAsync(compiled query) and you get Task<IReadOnlyList<T>>
thanks
Folks, today's International Marten's Day. We'll be giving today talks with @jeremydmiller showcasing Marten. See details:
Feel invited! :)
Hi! I have some questions regarding compiled queries
Should it be possible to correctly use compiled queries without parameters? When I do so and try to register the query type for code generation, it complains that the query is not a valid compiled query. If I add a parameter AND use it in the query, the registration seems to work fine.
Is it possible to use the tenancy helpers in a compiled query? e.g.
.Where(x => x.AnyTenant()). Same situation as above, when registering the query type.Should a where clause like this be possible:
.Where(x => x.ChildCollection.Any())?
We have all scenario's above in compiled queries and have not had any issues with them but we are now experimenting with up-front code generation and any query that uses any of the features above fail registration with storeOptions.RegisterCompiledQueryType()
ERROR: System.ArgumentOutOfRangeException: Application.SomeCompiledQuery.<>c is not a valid Marten compiled query type (Parameter 'queryType')
at Marten.StoreOptions.RegisterCompiledQueryType(Type queryType)
at Application.MartenServiceCollectionExtensions.RegisterCompiledQueryTypes(StoreOptions options) in ***\Startup.Marten.cs:line 94