Apache OpenOffice (AOO) Bugzilla – Issue 18437
wrong date value management in postgresql odbc access
Last modified: 2006-05-31 14:29:06 UTC
When trying to put an = condition using the designer on a date field, the sql sentence generate is not in some way accepted (see issue 17455 and 17500). On OORC3 you can switch designer off even if you have sql errors. So this is the sql generated (which give the problem) SELECT "cog", "nom", "scad", "emis" FROM "card" "card" WHERE ( ( "scad" = {D '2001-11-11' } ) ) To replace the error, simply select something on any table with a date field and write into criteria = A_DATE_VALUE.
i overtake
CLU->effevi: can you still reproduce this behavior in the oo1.1 final (or newer) version
set keyword: need more info
works for me in a final 1.1.0 CLU->effevi: i cannot repro that behaviot, may you please describe it more detailed? CLU->All: can anybody else repro it and give me a hint?
over two weeks no respond - looks like the problem is solved with newer version - so i close this issue
change subcomponent to 'none'