IMPORTANT Is using the underscore, considered upper case, ie needing quotes

Clifford Ilkay cilkay at
Mon Jan 29 20:01:39 EST 2018

To summarize what Doug Easterbrook and Jim have explained:

invoice_id - no need for quotes - GOOD

invoiceid - no need for quotes - GOOD

All other cases will need quotes and are not recommended for the reasons
that Doug explained.

InvoiceID - needs quotes

INVOICE_ID - needs quotes

INVOICEID - needs quotes

The same goes for table names and the names of other database objects, like
indexes, sequences, stored procecedures, etc.


Clifford Ilkay

+1 647-778-8696

On Mon, Jan 29, 2018 at 4:00 PM, Das Goravani <das at> wrote:

> Do you have to double quote a field name that uses an underscore, which is
> a shift key character, upper case, no?
> Does that cause the field to need double quotes ?
> I’m weeding out all the difficulty early on in my app which is in early
> stages of course.  I want to fix the naming conventions NOW.
> I removed upper case because it was going into the database and requires
> so many double quotes everywhere.
> If the underscore is just another upper case letter then I want to part
> with it as well.
> _____________________________________________________________
> Manage your list subscriptions at
> Start a new message -> mailto:omnisdev-en at

More information about the omnisdev-en mailing list