Mordechai Meisels
Mordechai Meisels
Can you please add minimal logging when running the code comparison via the views and the query fails? Currently it's a noop which made the reverse engineering so much harder.
I think it shouldn't be hidden behind an option. A crash in the query is most certainly a bug which needs attention.
What about array types? I think those also can't be quoted with the brackets
Tried it, getting this error (using postgres-js, but same error on node-postgres) ``` PostgresError: ROLLBACK TO SAVEPOINT can only be used in transaction blocks ```
I tried version 1.58.6 (which doesn't have this SAVEPOINT logic, but also doesn't deal with arrays yet). It crashed as expected, but the error is completely not helpful in any...
> This is fixed by the savepoints, so please try the latest version. But I tried and it fails with the error I posted earlier
Thanks @romeerez , just a nitpick about the docs, you reference `this.one` and `this.two` instead of hello world.
Starting to look like drizzle... I hope the existing config will be backward compatible, or at least, move to Orchid 2.0
Taking a second look at this issue after a year, yeps, definitely a nicer syntax with less boilerplate
I don't think it's worth making core changes and then having to deal with backwards compatibility just to remove the readonly keyword. It's definitely more compact, but if it doesn't...