|
From: SourceForge.net <no...@so...> - 2006-09-05 13:53:42
|
Bugs item #1507767, was opened at 2006-06-17 17:41 Message generated for change (Comment added) made by phd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1507767&group_id=74338 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General Group: SQLObject release (specify) >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Oleg Broytmann (phd) Summary: StringCol(char_binary=True) breaks if DBMS!=MySQL Initial Comment: StringCol(char_binary=True) is required by MySQL to allow case-sensitive comparisons for that column. However, for instance for SQLite this is not required. In the latter case "char_binary=True" should be ignored, but instead an exception is trown: ValueError: SQLite does not support binary character columns ---------------------------------------------------------------------- >Comment By: Oleg Broytmann (phd) Date: 2006-09-05 17:53 Message: Logged In: YES user_id=4799 "char_binary" was a somwhat experimental feature that I now very much recommend againts. "char_binary" in MySQL doesn't mean "case sensitive", it means "non-locale aware", which is very much different thing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1507767&group_id=74338 |
