Message-Id: <4.2.0.58.20000712131341.00ac0850@diligence.com>
Date: Wed, 12 Jul 2000 13:18:36 -0600
To: pgsql-interfaces@postgresql.org
From: Tim Uckun <tim@diligence.com>
Subject: ODBC and long object names.
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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

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.