Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Servio Velasco asked how to create case-sensitive table names. Art Kagel said to set DELIMIDENT and quote mixed-case names in double quotes. Jonathan Leffler clarified DELIMIDENT is needed in clients accessing such tables and not the server environment; setting it server-side forces SQL-standard quoting for all clients and cannot be overridden.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
I assume you mean the table, column, and other object names. Yes. You have
to set DELIMITED to 1 on the server's and user's environments and you will
havethe quote upper and mixed case object names like this:
"MyMixedCaseTableName"."ColumnName"
Art
On Oct 18, 2010 8:41 AM, "SERVIO VELASCO" <servio_velasco@hotmail.com>
wrote:
> Good Morning
>
> Exist any form to use case sensitive when I create table.
>
> Thank a lot
>
> Regard
>
> Servio Velasco
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
--0016e647697e5dda2e0492e4b82f
Hello Art.
I found DELIMIDENT. But Is It necesary set DELIMIDENT in both Server and
clients? and always use doble qoute (") to identfy tables and colums?
Regard
Servio Velasco
On Mon, Oct 18, 2010 at 08:57, SERVIO VELASCO
<servio_velasco@hotmail.com>wrote:
> I found DELIMIDENT. But Is It necesary set DELIMIDENT in both Server and
> clients? and always use double quote (") to identfy tables and colums?
>
You have to set DELIMIDENT in the clients that wish to access the
case-sensitive table names (and don't have to set it in the server
environment). Any case-insensitive table names can be left unquoted as
before.
You could set DELIMIDENT in the server environment, but you need to be
confident that all your programs conform to the SQL standard and use
single-quotes to surround strings (but double quotes to surround user names
on tables). And you'll have to be prepared to deal with any users who
aren't expecting that behaviour. If it is set in the server, there is no
way for the client to override the setting.
Are you sure you want to use case-sensitive names?
--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2008.0513 -- http://dbi.perl.org/
"Blessed are we who can laugh at ourselves, for we shall never cease to be
amused."
NB: Please do not use this email for correspondence.
I don't necessarily read it every week, even.
--20cf301d3da2d0c78d049325b1e4
Your privacy choices
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.