Hi, Andrea
I am about to finish my DB2FunctionTest. At the moment, there is only
a postgis implementation PostgisFunctionTest.
Some tests give me headaches. "testEuqalsIgnoreCase" is a good
example. The resulting postgis sql string is:
SELECT "id",encode(ST_AsBinary(ST_Force_2D("geometry")),'base64') as
"geometry","intProperty","doubleProperty","stringProperty" FROM
"public"."ft1" WHERE (lower("stringProperty") = lower('ZeRo'::text))
= true
The part after the were clause is interesting:
(lower("stringProperty") = lower('ZeRo'::text)) = true
Normally,
(lower("stringProperty") = lower('ZeRo'::text))
should be sufficient.
I have no chance to formulate "= true" in DB2 and I am not sure if
other databases support this construct.
Is there a special reason for that ?.
Should I override such test methods ?
Thanks in advance
Christian
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
