On Apr 15, 2006, at 3:27 PM, Jan Erik Moström wrote:
Well, I'm going to take the easy way out: pretend that the problem
doesn't
exist ;-)
I'll build my application and see if it will actually work as I
want, then
warn my users (if I get any) about the problem ... and if I ever
get the
money to pay for a proper database implementation I'll fix it.
Why not make my own "escape code"? I don't trust myself on covering
all cases
(I don't know SQL that good to know everything) and I'll rather
spend my time
implementing the rest of the application.
For a single database it should be possible to write the correct
escape code_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
