From: Tim Uckun <tim@diligence.com>
To: pgsql-interfaces@postgresql.org
Subject: ODBC and long object names.
Date: Wed, 12 Jul 2000 13:18:36 -0600
Message-ID: <4.2.0.58.20000712131341.00ac0850@diligence.com> (raw)
In-Reply-To: <24282.963425767@sss.pgh.pa.us>
References: <Pine.LNX.4.21.0007111052420.8323-100000@nanu.visionforisrael.com>
<Pine.LNX.4.21.0007111052420.8323-100000@nanu.visionforisrael.com>
I am not sure if this a bug report or a feature request.
When I compiles postgres I changed the NAMEDATALEN #DEFINE to 64 ( a more
reasonable length for object names IMHO). So far it has not caused any
problems with postgres but it is causing problems with the ODBC driver.
When I attempt to attach any table who has a long object name or an
associated index with a long name it causes an error message and does not
connect. It seems like it's returning a null or an empty sting or something.
There was talk a while ago about Postgres changing NAMEDATALEN a while back
so this might become more important if the official disto gets changed.
:wq
Tim Uckun
Due Diligence Inc. http://www.diligence.com/ Americas Background
Investigation Expert.
If your company isn't doing background checks, maybe you haven't considered
the risks of a bad hire.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tim@diligence.com
Subject: Re: ODBC and long object names.
In-Reply-To: <4.2.0.58.20000712131341.00ac0850@diligence.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox