Evgenij Ryazanov

Such alternative syntax may be accepted in Oracle compatibility mode if somebody really need it (do you?), but I don't think that it should be supported in all modes including...

But what exactly do you need for jOOQ? Acceptance of this in Oracle mode? Acceptance of this with some other flag? Nothing?

OK, I think in this case we can wait until somebody else comes to raise this issue up. You mentioned some databases with alternative syntax. H2 has compatibility mode for...

However, thank you for investigation. Your information may help to choose proper way to implement such feature if it will be necessary.

2.1.210 is the first release in 2.1 series of releases, there were two bugfix releases and it is more reasonable to use 2.1.214 instead of 2.1.210. RUNSCIPT command usually needs...

Do you really need `BINARY(262144)` columns? `FROM_1X` converts them to more reasonable `BINARY VARYING(262144)` data type. `BINARY` is a fixed-width data type, too short values are right-padded with `X'00` to...

I have no idea how they can disappear too. This exception also doesn't look like an exception caused by database corruption.

Unfortunately, there is nothing to do with this issue unless you can provide a complete test case. > Also, some of my tables don't have Primary Key. Tables aren't required...

`BINARY(262144)` instead of `BINARY VARYING(262144)` changes all persisted values to byte arrays with exactly 262144 bytes. If you had shorter values, they will be changed, I don't think you want...

Data type replacement from `BINARY` to `BINARY VARYING` during upgrade is only required for databases where `BINARY` data type was used incorrectly for variable-length values instead of `BINARY VARYING`. (In...