**
** are you using mySQL NT?
**
** Here's something to try... FORWARDslash instead of a
** backslash. yes, I know
** it sounds wrong, but it just may work. I use mySQL and in my cnf file
** there's a line that reads
That's how mysql needs it to be. Many unix ports are the same way, though
some are more forgiving than others.
**
** temp=c:/temp (not temp=c:\temp like you think it should be).
** it took me
** five weeks to figure this one out.
Since Imail needs to retrieve this value, it will end up with the "wrong"
slashes instead of the standard backwards slash that it needs to open the
file. In short, it won't work.
What needs to happen here, is to hack the necessary code into Mike's
source. It should be fairly trivial.
Another option, would be to make a MySQL specific implementation of the
ODBCUSER.DLL using the MySQL C API, which includes a
mysql_real_escape_string() function that will take whatever you throw at
it and escape out the special characters as needed. This would have the
added benifit of eliminating the overhead of the ODBC abstraction layer,
increasing performance a tad bit.
**
** this leads me to think that mySQL uses forward slashes. IMHO,
** MYsql NT is a
** poor NT port of a unix app.
What do you expect for software ported to a poor implementation of an OS?
I haven't used MySQL NT (the Unix version is /FREE/ after all. I expect
that the data storage would work the same way on both the Unix and NT
version. The escape characters shouldn't change between implementations.
If you really want to get into it, check out Visual C. It still uses \n
for a newline, and \t for a tab, and \\ for a \. It makes one wonder why
DOS used the backslash instead of the slash as it's path delimiter, and
why Microsoft continues to do it this way still. (I also wonder why MS
still uses those damned drive letters).
-Troy
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
