Re: login errors

[john <..hidden..>]

There is another error i came across when using PG 8.3 when adding a
vendor invoice:

------------------------------------
DBD::Pg::st execute failed: ERROR: operator does not exist: integer =
text
LINE 3: WHERE c.id = (SELECT value FROM defaults 
^
HINT: No operator matches the given name and argument type(s). You might
need to add explicit type casts.


Error!

SELECT (select c.accno FROM chart c 
WHERE c.id = (SELECT value FROM defaults 
WHERE setting_key = 
'inventory_accno_id'))
AS inventory_accno,

(SELECT c.accno FROM chart c
WHERE c.id = (SELECT value FROM defaults
WHERE setting_key =
'income_accno_id'))
AS income_accno,

(SELECT c.accno FROM chart c
WHERE c.id = (SELECT value FROM defaults
WHERE setting_key =
'expense_accno_id'))
AS expense_accno,

(SELECT c.accno FROM chart c
WHERE c.id = (SELECT value FROM defaults
WHERE setting_key =
'fxgain_accno_id'))
AS fxgain_accno,

(SELECT c.accno FROM chart c
WHERE c.id = (SELECT value FROM defaults
WHERE setting_key =
'fxloss_accno_id'))
AS fxloss_accno, 
(SELECT value FROM defaults
WHERE setting_key = 'curr') AS currencies,
current_date AS transdate
ERROR: operator does not exist: integer = text
LINE 3: WHERE c.id = (SELECT value FROM defaults 
^
HINT: No operator matches the given name and argument type(s). You might
need to add explicit type casts.
------------------------------------


i experienced similar errors when adding parts and services, but do not
have the exact error message.

john


On Wed, 2008-01-30 at 18:31 -0800, Chris Travers wrote:
> 
> 
> On Jan 30, 2008 5:41 PM, Joshua D. Drake <..hidden..> wrote:
>         -----BEGIN PGP SIGNED MESSAGE-----
>         Hash: SHA1
>         
>         On Wed, 30 Jan 2008 10:18:18 -0800
>         "Chris Travers" <..hidden..> wrote:
>         
>         >
>         > Our first PgSQL 8.3 compatibility bug.  Please try the
>         latest
>         > Session/DB.pm from svn branches/1.2
>         
>         
>         /me grumbles about 8.3 not being out yet!!
>         
>         There are other likely very big compatibility issues with 8.3.
>         8.2.6
>         should be the recommended platform. I think we are asking for
>         trouble
>         if we spend a bunch of time making 1.2 work with 8.3.
> 
> Almost certainly there will be more problems.
> 
> Of course, *most* of them will affect both 1.2 and 1.3.  And they are
> trivial to solve once we get a bug report.
>  
>         
>         
>         Let's focus on 1.3 :)
> 
> Agreed.  However, we have agreed that we will fix bugs reported when
> PostgreSQL 8.3 is used with 1.3 even if we won't make any guarantees
> about things working error-free out of the box.  I think this is the
> best policy.  Most of the work in getting stuff to work with PgSQL 8.3
> is going to be in testing.  As far as I am conerned, the 2 min. it
> took to fix this in 1.2 is not a bad thing (2 min for branches/1.2 and
> 30 sec. or so for /trunk).  I just don't want to spend 20 hours trying
> to test the application on PgSQL 8.3 in order to ensure it works.
> 
> So, my feeling is that if people want to run PostgreSQL 8.3, the
> appropriate response from us is "we make no guarantees but will fix
> reported issues."
> 
> 
> Best Wishes,
> Chris Travers
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________ Ledger-smb-users mailing list ..hidden.. https://lists.sourceforge.net/lists/listinfo/ledger-smb-users