To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=75699





------- Additional comments from [EMAIL PROTECTED] Wed May  2 02:25:06 +0000 
2007 -------
Data:

id     acct_mo_yr                  acct_day    value_a     value_b

0      04/01/2007 00:00:00         1           2.000         3.000
1      03/01/2007 00:00:01         4           5.000         6.000
2      02/01/2007 00:00:02         7           8.000         9.000

Query 1:

In the query design grid I placed: 4/1/2007 00:00:00

SQL statement generated:

SELECT "id", "acct_mo_yr", "acct_day", "value_a", "value_b" FROM "Table1" WHERE
( ( "acct_mo_yr" = {D '2007-04-01' } ) )

With the embedded HSQL database, the query grid translation to a date only
format produces the record number 0 without any problem. 

Query 2:

In the query design grid I placed: 3/1/2007 00:00:01

SQL statement generated:

SELECT "id", "acct_mo_yr", "acct_day", "value_a", "value_b" FROM "Table1" WHERE
( ( "acct_mo_yr" = {TS '2007-03-01 00:00:01.0' } ) )

Add a second to the time field and the query design grid translation results in
the correct TS type in the SQL statement.

This is what I expected with Query 1. Additionally, if the time portion wasn't
specified in the criteria, I would expect it to default to 00:00:00 in the
resulting SQL statement as a time stamp field to match the underlying DB field
definition.

Using either Informix 3.30 or Intersolv 3.11 ODBC drivers, this translation to a
date only type SQL statement when the time portion is 00:00:00 causes/returns a
data type mismatch error as the field being referenced is defined as being a
time stamp type in the DB which the driver is respecting. It's expecting a time
stamp value and complains when it's presented with something else. Close isn't
good enough.

(In my case, the DB has this field defined as a time stamp data type, even
though the actual data is always day 1 of any given month/year with the time
portion always being 00:00:00. I can't change this, I just have to work with 
it.)

I'll attach my sample data base to demonstrate the issue.


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to