Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id CD8859FB3CA for ; Thu, 12 Jul 2007 14:48:53 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 02164-07 for ; Thu, 12 Jul 2007 14:48:41 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 2EA7C9FB3C5 for ; Thu, 12 Jul 2007 14:48:46 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l6CHmeCe001571; Thu, 12 Jul 2007 13:48:40 -0400 (EDT) To: Joel Richard cc: sql pgsql Subject: Re: Converting from MS Access field aliases In-reply-to: References: <746273.93291.qm@web54305.mail.re2.yahoo.com> <634.1184260980@sss.pgh.pa.us> Comments: In-reply-to Joel Richard message dated "Thu, 12 Jul 2007 13:36:05 -0400" Date: Thu, 12 Jul 2007 13:48:40 -0400 Message-ID: <1570.1184262520@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/70 X-Sequence-Number: 28805 Joel Richard writes: > What's really screwy is what I found when I hooked access into my > PostgreSQL database using pgsqlODBC (I know, it's an abomination) and > I logged the statements that PostgreSQL was processing. In MS Access > this query: > SELECT foo AS bar, bar * 2 AS gleep FROM table; > became this in PostgreSQL's logs > SELECT foo FROM table; > Vewwy Intewesting! Yeah, that *is* interesting --- it means Access is trying to do all the arithmetic for itself. I guess this means that you could keep using the statements unchanged if you wanted to use Access as a frontend to Postgres. Of course you're trying to get away from that, but this might at least give you a chance of fixing things incrementally instead of having to fix everything all at once. regards, tom lane