Michael J. Sullivan
Michael J. Sullivan
Darn, I realized as I merged that I didn't update the comment - I *did* add a future
I am -1 on adding any SQL-inspired warnings to queries that compile correctly, but I think it would probably be a good idea to add hints to certain errors; especially...
Could you post your schema/migrations, or email them to me at [email protected], with directions to repo? This seems nasty but there's not really anything I can do with the report...
You might be on to something with the data-only export idea, but first I want to talk about your dump/restore failures, which are a serious problem. I have some questions:...
Oh, I guess the logs that might be useful here or the *postgres* logs. > Theoretically, does this mean that we can choose to export EdgeQL statements separately for our...
Could you check the postgres logs to see if it has some error when the failure happens?
@elprans did you have some idea about what data to check for debugging questions?
We now support RepeatableRead for many operations and PreferRepeatableRead in the clients, which has helped a lot here.
I found one problem while poking around with testing: ``` _localdev:main> select schema::Array { name } filter .name = 'array'; {} _localdev:main> create global compositeAA -> array; OK: CREATE GLOBAL...
Why is it a bug? Shouldn't it return 0 then? What am I missing?