El Martes, 19 de Enero de 2010, Iñaki Baz Castillo escribió: > El Martes, 19 de Enero de 2010, Iñaki Baz Castillo escribió: > > El Jueves, 14 de Enero de 2010, Jeremy Evans escribió: > > > while PostgreSQL and MySQL are case sensitive for like and case > > > insensitive for ilike. > > > > This is not what happens in my system: > > > > MySQL 5.1.30 (Ubuntu) behaves case insensitive for "LIKE" and "=" > > operators when using them in a type "char" field. > > > > I need "=" to be case sensitive but I use prepared statements: > > > > DB[table]. \ > > filter(:user => :$n1, :doc_uri => :$n2). \ > > select(:id, :etag). \ > > prepare(:first, :ps01) > > > > I suspect I must configure my MySQL server to behave as case insensitive, > > right? > > It seems that BINARY, VARBINARY, BLOB are required for case sensitive > comparisons: > > http://dev.mysql.com/doc/refman/5.0/en/case-sensitivity.html
Other solution is setting COLLATE "latin1_general_cs" (or any ending in "_cs") for the column. Is it possible Sequel to generate a DB column with specified collation? -- Iñaki Baz Castillo <[email protected]>
-- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
