On Sun, 2023-01-15 at 22:15 -0800, AndyGo wrote:
> If I'm writing all SQL by hand then personally, I'm going to always
> use unquoted values for table/view names.
Working with Oracle, H2, MS SQL Server and DB2, I think best practise
was to write SQL Keywords "lower case" and Identifiers "upper
Greetings Andy.
On Sun, 2023-01-15 at 22:15 -0800, AndyGo wrote:
> I'm going to always use unquoted values for table/view names.
This is not RDBMS agnostic and will get you into big trouble when
switching from Oracle to Sybase or MS SQL Server or vice versa.
> I've used H2 successfully in
Thanks for the reply andrei.
It's not a matter of trying to shoot myself in the foot. If I'm writing all
SQL by hand then personally, I'm going to always use unquoted values for
table/view names. However, various ORMs and query tools/frameworks have all
kinds of different behaviors.
I've used
Hi Andy,
I wonder, what are your expectations in such scenario?
If you are looking for a way to shoot yourself in the foot, I am sure H2
will present multiple opportunities for that.
Does it really matter if it end up with "table not found" or will select
from one or the other table, at random?
Thanks. Appreciate the quick and comprehensive response. Can you explain
this a bit more: "It is possible to specify them in the default Regular
compatibility mode "
Just curious, since the settings can't persist... what would happen if, in
default mode, I created MyTable and also "mytable"
Hello!
These settings aren't related to each other.
IGNORE_CASE is about *data types* and their *values*. It replaces CHARACTER
VARYING (VARCHAR) columns in DDL commands with VARCHAR_IGNORECASE data
type. This legacy setting should never be used, it is much better to
specify some
