#986: MySQL database support
----------------------------+-----------------------------------------------
Reporter: anonymous | Owner: jonas
Type: enhancement | Status: reopened
Priority: high | Milestone: 0.10
Component: general | Version: devel
Severity: major | Resolution:
Keywords: database mysql |
----------------------------+-----------------------------------------------
Comment (by Andres Salomon <[EMAIL PROTECTED]>):
Regarding the like() function, it looks like SQLite's LIKE supports case-
insensitive matching by default (with a caveat), postgresql has ILIKE for
that sort of thing, and mysql's LIKE is case-sensitive depending on the
column type. If it's a plain VARCHAR, LIKE matches in a case-insensitive
manner. If it's a VARCHAR BINARY type, LIKE matches in a case-sensitive
manner. Ugh.
I think it would make more sense (and be less complex) to simply use
LOWER() on arguments here, to ensure we're doing a case-insensitive match.
If you folks agree, I'll follow up with a patch.
Oh, and the SQLite caveat?
"(A bug: SQLite only understands upper/lower case for 7-bit Latin
characters. Hence the LIKE operator is case sensitive for 8-bit iso8859
characters or UTF-8 characters. For example, the expression 'a' LIKE 'A'
is TRUE but 'æ' LIKE 'Æ' is FALSE.)."
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/986>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
