Re: DB2 for i SQL naming conventions

UPPERCASE_WITH_UNDERSCORES

Is really the only option..

You can't use Mixed case in Db2 for i _UNLESS_ you double quote the names

so
create "My_Table"

means you always need
select * from "My_Table"

whereas
create MY_TABLE
or create my_table

means you can use
select * from my_table
select * from MY_Table
select * from My_Table
ect...

Charles


On Fri, Aug 6, 2021 at 3:54 PM <lee_paul@xxxxxxxxxxxxxxxx> wrote:

When creating Tables, Indexes, Views, Functions, or other SQL-based objects
on the IBM i, what do you use for your naming conventions?



Object naming for multiple word separation: Do you use UpperCamelCase or
UPPERCASE_WITH_UNDERSCORES or Upper_Camel_Case_With_Underscores?



Constraint Naming: What do you name your different constraints?



Where do you store your SQL Source? QSQLSRC?



What other standards and conventions should I be thinking about when
creating SQL objects on the IBM i?









--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com