Message-Id: <36DD89B6.975FCA41@insightdist.com>
Date: Wed, 03 Mar 1999 14:12:54 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Mime-Version: 1.0
To: "Christopher R. Jones" <cj@interlog.com>
Cc: PostgreSQL Interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] postdrv ODBC driver problems
References: <36DCB277.498738E0@alef.gcsu.edu>
	<3.0.5.32.19990303135807.00936540@mail.interlog.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Christopher R. Jones wrote:

> >Yes, it is a known problem with mixed case.  Some Microsoft apps don't
> >bother to use quotes around table/field names to preserve the case, I guess
> >cause they assume that every dbms works like Microsoft SQL server.  MSAccess
> >however does always use quotes so mixed case names are no problem with
> >MSAccess.
> >
> >I'm not really sure how to proceed on this one.   Maybe you could just use
> >all lower case names for now.
> >
> >It would seem to me that if an identifier (table/field name) is not quoted
> >in an sql statement, then Postgres should not care about the case and match
> >on it.  That to me seems like the correct approach.
> >
> >Any opinions?
> >
> >Byron
> I have always thought it strange that Access would allow field names with
> mixed case and spaces.  I come from the Foxbase side and Visual Foxpro has
> maintained the tradition of lower case, no space field names.  It
> simplifies things to stick to one naming convention that works for all
> databases.

MSAccess checks to see if the driver supports quoted identifiers.  If it does, it
allows the spaces and mixed case in field/table names.  If it doesn't, it does
not allow those things.

Byron