Closed patrickkusebauch closed 2 years ago
Will look into it asap, super busy these days.
@prolic @fritz-gerneth any ideas what would be the best way to solve the problem?
a) Escape dots in aggregate id by default b) Document that a custom stream strategy should be used in this case
@codeliner not directed at me, but I think just documenting it is a bad idea. At least, it should throw an Exception. But then you would need to change to the method signature. That would be a breaking change. Escaping by default would be great.
I tried to look into this today. I don't think there is a solution to this problem without BC. Everything before the dot is treated as the schema name (in postgres that's "public" by default) but can be any other schema as well.
I suggest you use another delimiter for separation of aggregate name and id.
@codeliner @fritz-gerneth @enumag thoughts?
A breaking change is no option at this point and I also don't have another idea. One needs to accept this limitation. Since AggregateStreamStrategy is not the best choice for most use cases because projections are too slow (see note here), I consider this an edge case. I'm not happy with it, but time is limited.
Failing test for issue #226