Issue 18437 - wrong date value management in postgresql odbc access
Summary: wrong date value management in postgresql odbc access
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC3
Hardware: Other Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: christoph.lukasiak
QA Contact: issues@dba
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2003-08-20 08:27 UTC by effevi
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description effevi 2003-08-20 08:27:38 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.
Comment 1 christoph.lukasiak 2003-11-26 10:38:45 UTC
i overtake
Comment 2 christoph.lukasiak 2003-11-26 10:40:58 UTC
CLU->effevi: can you still reproduce this behavior in the oo1.1 final
(or newer) version
Comment 3 christoph.lukasiak 2003-11-26 11:12:48 UTC
set keyword: need more info
Comment 4 christoph.lukasiak 2003-12-01 17:05:13 UTC
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?
Comment 5 christoph.lukasiak 2003-12-15 14:53:27 UTC
over two weeks no respond - looks like the problem is solved with newer version
- so i close this issue
Comment 6 hans_werner67 2004-02-02 12:14:34 UTC
change subcomponent to 'none'