Skip site navigation (1) Skip section navigation (2)

RE: select statement

From: Cedar Cox <cedarc(at)visionforisrael(dot)com>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: "'Joseph'" <lters(at)mrtc(dot)com>, pgsql-odbc(at)postgresql(dot)org
Subject: RE: select statement
Date: 2001-06-24 09:41:43
Message-ID: Pine.LNX.4.21.0106241236310.10751-100000@nanu.visionforisrael.com (view raw or flat)
Thread:
Lists: pgsql-odbc
On Thu, 21 Jun 2001, Dave Page wrote:
> 
> > -----Original Message-----
> > From: Joseph [mailto:lters(at)mrtc(dot)com] 
> > Sent: 21 June 2001 11:54
> > To: pgsql-odbc(at)postgresql(dot)org
> > Subject: [ODBC] select statement
> > 
> > 
> > Why does the odbc driver sometimes put a
> > 
> >  'select * from'
> > 
> > in front of select statments?
> > 
> > It seems to only do it sometimes...
> > 
> > respectfully,
> > Joseph 
> 
> This is often done by Microsoft DAO or ADO when you specify commandtype =
> Table on a datacontrol or similar. If you specify commandtype = Text this
> will not happen.
> 
> HTH, regards, Dave.

I've noticed this with Access.  Seems that if Access gets an error from
the backend, eg. from invalid SQL, it will add 'select * from' in front of
the SQL and try again (most of the time this will fail also..  As far as I
can see, this is so that you can use just a table name instead of a SQL
statement for a datasource (like you can with Access/Jet) and it will
work.

-Cedar


In response to

pgsql-odbc by date

Next:From: Olivier BergerDate: 2001-06-25 09:02:53
Subject: Write access problems with StarOffice for Windows
Previous:From: Richard HuxtonDate: 2001-06-22 16:08:25
Subject: Re: Difference between insert a tuple in a table by function and by datasheet

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group