The problem with parsing SQL on the client is that sooner or later you
will get smarter, have new requirements, or probably both. Then you
will need to change the encoding. When that happens either a) you will
invalidate old clients, or b) the server will have to handle legacy
encodings forever. Neither is particularly palatable. If you are
convinced that you will never have a better idea or are willing to stick
with bad ideas if you have a better one, by all means save a few
microseconds with an unnecessarily complex and bloated client.
The really nice thing about SQL is that it's character based (oops, I
almost said ASCII), so SQL can change without changing the plumbing.
A small client is a happy client, and a smaller client is an even
happier client. The best way to do thing is to make the client 100%
plumbing and 0% database semantics.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
