>From my testing, using this option allows the USER to override the SYSTEM 
alias'

However, this option does not allow the SYSTEM to override the USER alias'

What this means is that with the option turned on, the user can create a 
function (e.g. date_trunc) that overrides the systems function

However, if an existing database is loaded with a user alias (e.g. 
date_trunc) that overlaps with a new system function, the system will be 
unable to start because it cannot override the user function.
An unfortunate consequence of this is that the user is unable to issue a 
command to delete the alias, as they cannot connect to the database.

Is this correct?


On Tuesday, 27 March 2018 10:43:47 UTC+1, Noel Grandin wrote:
>
> You could connect with the old version of H2, drop the alias, then 
> reconnect with the newer version. 
>
> Or you can use connect with this in your connection string 
>
>     BUILTIN_ALIAS_OVERRIDE=1 
>
> to allow you to temporarily override the system alias. 
>

-- 
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

Reply via email to