|
From: Dieter S. <dsi...@sq...> - 2002-02-20 01:37:14
|
You have to upgrade to postgres 7+ subselects are not supported in pre 7 versions. Dieter Simader http://www.sql-ledger.org (780) 472-8161 DWS Systems Inc. Accounting Software Fax: 478-5281 =========== On a clear disk you can seek forever =========== On Wed, 20 Feb 2002, Craig Nunemaker wrote: > I checked psql and neither worked. After doing some reading on postgresql, I noticed > single quotes. The following worked in psql: > > SET DATESTYLE to 'ISO' > > I edited my user.conf in the dboptions line to use single quotes. It worked. > > However, now my AR and AP module give me the following parser error when trying to > Add a Transaction. > > SELECTcurrent_date AS transdate, current_date + 30 AS duedate, d.curr AS currencies, > (SELECT c.accno FROM chart c WHERE d.fxgain_accno_id = c.id) AS fxgain_accno, > (SELECT c.accno FROM chart c WHERE d.fxloss_accno_id = c.id) AS fxloss_accno > FROM defaults d > Parser error at or near "select" > > I ran it piecemeal through psql and ran into problems at the subquery. > > BTW, I am using a Debian Woody default installation with Perl DBI. > > > 2/19/02 1:27:33 PM, Dieter Simader <dsi...@sq...> wrote: > > >Hi Craig! > > > >load psql and type in > > > >SET DATESTYLE to ISO > >SET DATESTYLE to "ISO" > > > >let me know which one works. > > > > > >Dieter Simader http://www.sql-ledger.org (780) 472-8161 > >DWS Systems Inc. Accounting Software Fax: 478-5281 > >=========== On a clear disk you can seek forever =========== > > > >On Mon, 18 Feb 2002, Craig Nunemaker wrote: > > > >> Has anyone ever gotten a DateStyle parse error? > >> > >> After logging in and clicking on any module action the screen displays the follwing > error: > >> Error: Set DateStyle to "ISO" > >> Parse error at or near ISO > >> > >> I checked my Apache error log and found the following entry. > >> DBD::Pg:db do failed: ERROR: parse error at or near "iso" at SL/Form.pm line > >> 431 > >> Error: set DateStyle to ISO<br>ERROR: parser: parse error at otr near "iso" > >> Database handle destroyed without explicit disconnect. > >> > >> I examined SL/Form.pm but could not figure out how the code itself would raise an > error. > >> > >> > >> > >> > >> > >> > >> NOTICE: When replying, please Reply to the list address. This way other members > know if the issues have been resolved or not. Thanks! Your List administrator. > >> > >> > > > > > > > > |