on 10-12-2011 3:44 PM
Hi,
we ran into a bug in the query parser while testing our system with japanese dates, that crashes the kernel when a date/time/timestamp field is compared to a literal that contains a unicode character.
For instance,
select * from dual where now() = '2011年10月12日'
will crash the kernel (7.7 or 7.8)
Normally the date field should be compared only with strings in ISO format, but we fear some wrongly written query will crash our production database.
Is that a known bug and is there a workaround ?
Guillaume
Hi Guillaume,
this is a bug whereas not a known one up to now. We will solve this ASAP and have created an entry in our error database: [1239879|http://maxdb.sap.com/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1239879].
Unfortunately there is no other workaround for this error than not to use UNICODE characters in those queries.
Thank you for reporting.
Best regards,
Steffen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
92 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.