I have max_allowed to 128M on server. And I insert blobs all the
time, but first with mysql. Its not just witango, I am inserting with
other APIs, and they all only inserting the first four bytes.
Normally the odbc driver, does the escaping for you, but even when I
am using VB, I have to escape myself first. And am finding this to be
the case with other stuff I have read. Dunnow if issue with latest
drivers. I also have the option set, on the client side to allow
large packets.
Anyway, I know it is not server, cuz when I do hex first, or use VB
and escape, I can insert images just fine.
--
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/
On Mar 27, 2006, at 2:10 PM, William M Conlon wrote:
Hi Robert,
I regularly insert blobs into mysql, and in fact had an example in
NCOL's Witango contest a few years ago. Let me know if you can't
find it.
A couple of things to pay attention to:
You must use an Insert Action, as <@BIND> chokes on blobs larger
than 32k.
Pay attention to the mysql max-allowed_packet. In my.cnf, add
something like:
set-variable = max_allowed_packet=10M
this will allow 10 megabyte files. The default is a one megabyte
file.
On Mar 27, 2006, at 12:28 PM, Robert Garcia wrote:
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
Bill
William M. Conlon, P.E., Ph.D.
To the Point
345 California Avenue Suite 2
Palo Alto, CA 94306
vox: 650.327.2175 (direct)
fax: 650.329.8335
mobile: 650.906.9929
e-mail: mailto:[EMAIL PROTECTED]
web: http://www.tothept.com
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
