I am not an expert with mysql, I have used oracle, ms, and primebase
extensively, but have a client that needs some stuff for mysql.
First, inserting blobs. With the other dbs I have used, I just do an
insert or update, and pass the binary string in, and witango has done
the rest, mysql burps.
As a workaround, I have used witango to hex the binary string, and
then I use mysql UNHEX('thestring') on insert. I don't like the
overhead of this, and reading around, it seems the mysql string needs
to be escaped, but I would have expected witango to do this, anyway,
is there a flag in the odbc setup, or something I am missing on this
one?
Also, witango has a whole set of reserved words, and a few we are
using as column names unfortunately, and don't want to change. This
is super easy to get around in any other language, you just qualify
column like `colname`, and it works fine. But you can't do that in
witango, without doing custom columns, directDBMS, or I found a way
to edit taf manually to get to work, but its a pain. Wondering if
anyone else has coped with this.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
