ODBC and long object names.

From: Tim Uckun <tim(at)diligence(dot)com>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: ODBC and long object names.
Date: 2000-07-12 19:18:36
Message-ID: 4.2.0.58.20000712131341.00ac0850@diligence.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

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.

In response to

Browse pgsql-interfaces by date

  From Date Subject
Next Message Joseph Shraibman 2000-07-13 02:35:22 select for update not locking properly.
Previous Message Jonathan Marchand 2000-07-12 18:45:23 Re: Re: Subject: IIS4 ODBC LOGGING TO POSTGRES - CRASH HELP :)