[feature] Custom builds or Disable Schema validation

[natew]

Actual use case for me is Schemas. It's been a year we've been in development, and there are days where I change the schema ~10 times, and end up clearing data each time.

I do see a way to automate writing migrations, but then we'd be committing new versions/migrations, a lot.

I do want migrations once we go into production, but for development it's enough of a nuisance to want to be able to disable them.

Just documenting the desire here.

[pubkey]

The schema-validation is required. At the moment the documents do not match the schema, you will have big trouble with errors that are hard to debug. Many things like the proxy-getters and the QueryChangeDetection can only work I the schema is valid. Therefore this 'feature' is made especially to use in developement. At the moment you ship code to prod and find out that the schema does not match your data, its too late.

I recommend to use the memory-adapter for dev, so you do not have to clear up data after each dev-cycle.

One think I could do was allowing the recreation of a collection, if it does not contain any documents. See

Hope this helps a bit.

[natew]

Actually this is a decent solution -- can easily delete all docs in dev mode. Thanks a ton.