Brian Aker wrote:
Hi!
On Aug 14, 2008, at 11:47 AM, Roy Lyseng wrote:
If the code is there already, is there a reason to toss it? It
provides some flexibility, the code should be fairly clean (ie no
maintenance issue), and there is certainly no performance impact.
The code is not complete which is one reason to replace it. I would be
happier to use a library that many projects use over us maintaining
something which is just ours (more eyeballs the other way).
Right now using character sets and collations is messy with MySQL. We
are looking for something which is a bit cleaner.
I guess you are talking about the actual charset/collation support? My
point was about the flexible default handling.
For collation handling the complexity lies in supporting either one or
multiple collations. If you support multiple collations, a flexible
default handling scheme does not add much code complexity.
Thanks,
Roy
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp