On 2021/02/19 9:27 am, Evgenij Ryazanov wrote:
New data types will definitely require massive changes everywhere.
Yup, that's what I meant by deep vs shallow integration.
If the new datatypes are just aliases over existing types, it's not a problem.
If the new datatypes want proper compatibility with PostgeSQL, then we would have to see how much compat we can supply
before we draw the line and say "this is too disruptive".
On the up side, such new datatypes would give us an initial idea of the
requirements for UDTs.
And I dont think we need to follow the SQL-Standard design for UDTs - nobody
else does.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/h2-database/a3e32913-724c-b2c3-3bfd-b952921bb678%40gmail.com.
