Prepared statements in embedded MySQL

2003-12-10 Thread Richard Tibbetts
I was wonder if anyone here could comment on when prepared statements might be available in the embedded server, I would find it very helpful. Will they be in the 4.1 release? Are there plans to add support in some future release? Thanks, Richard Tibbetts -- MySQL General Mailing List For list

Re: email attachments, stripped, coverted to text and inserted into MySQL

2004-01-13 Thread Richard Tibbetts
On Tue, Jan 13, 2004 at 09:41:57AM -0400, Vernon Webb wrote: > I've been asking around for awhile without a solution to this > problem and thought I'd post it here perhaps some one will know of a > script that will help. > > I need to have emails sunmitted to a database field but more to the > poi

Re: anybody used prepared statements in 4.1 succesfully?

2004-01-22 Thread Richard Tibbetts
Since you aren't using the C API directly, you should make sure your API is actually using prepared statements. I don't know anything about Connector/J, but for example, last I checked, the Perl DBI mysql modules didn't really prepare statements when you called the prepare method. This is of cours

Re: anybody used prepared statements in 4.1 succesfully?

2004-01-22 Thread Richard Tibbetts
If you have the right level of logging turned on, you will see evidence in your query log. Generally you see command sequences like Connect, Query, Query, Query, Quit. With prepared statements you would see Connect, Prepare, Execute, Execute, Execute, Quit. I don't know off hand if there is a go

Re: anybody used prepared statements in 4.1 succesfully?

2004-01-22 Thread Richard Tibbetts
On Thu, Jan 22, 2004 at 01:51:09PM +, Brian Power wrote: > do any of the dudes involved with mySQL read this forum ? > > even though I didn't pay for support would they respond to a direct email ? My experience is that if you aren't filing rock-solid bug reports, and you aren't paying, the de

C API Prepared Statement Interface - MYSQL_BIND

2003-11-19 Thread Richard Tibbetts
ql_bind_param() uses buffer_length to tell the server about the max argument length, and that mysql_execute() uses length to decide how much data to actually send for a given invocation. Is this correct? Thanks, Richard Tibbetts -- MySQL General Mailing List For list archives: http://lists.mysql.com/