Marios Trivyzas
Marios Trivyzas
@proddata do we also need `first`/`last` aliases for those?
- [x] Parser changes - [x] Analyzer + Plan changes for ROLEs - [x] Introduce `RolesMetadata` but continue reading `UsersMetadata` to be able to restore old snapshots - [x] sys.roles...
Thx for reporting this improvement @proddata, it has been implemented with #13528
yep, I see, just from the PR title this seemed finished, but also fine to keep it open until everything is addressed, thx!
Not important, as you like, if it's more clear with a separate issue, you could open it.
Since we're going to use drop column and then re-add it with the new data type, we need to document that if the table is already populated, the existing data...
For future reference: We tested and verified that: - with the updated key, `.rpm` and `.deb` users with the old public key can install new packages, signed with the updated...
I kind of prefer @romseygeek's suggestion, or something similar. I'm sceptical regarding the Input solution, when I see this: https://github.com/crate/crate/pull/15765/files#diff-8b855ba352a12dde36505be36a145486feefcc303ab2f45e5c76019b1dd944f6R213 which means apart from going through existing usages, we don't...
Apologies, I didn't phrase it correctly, of course you have to somehow use `try-with-resources` or explicitly call `close()`, I'm skeptical about the fine grain level, of following this, if it's...
I've tried out to implement this, and the issue I'm facing is the overload of the function where the user passes `tableOid` instead of a table, view, foreign table name....