Header changes between 5.0.27 and 5.0.51?

Hello, Running a FreeBSD system and mysql 5.0.27 server, I'd like to upgrade to 5.0.51. I would like to know if there are 'header' changes between the two versions? I mean, do I have to recompile my various Perl clients, mod_mysql for PHP, etc? Or can they stay linked against libmysqlclient.

Re: best practice MySQl backup onto tape

Hi, Keith, In my case, it is just single MySQL server(no replication). Thanks for your info, I'll check with mk-parallel-dump tools, since the speed of backup is important considering the database is locked for the duration of the backup. Regards, Jenny On 12/14/07, B. Keith Murphy <[EMAIL PRO

Re: best practice MySQl backup onto tape

Jenny Chen wrote: Hi, I'm planing to do hot backup MySQL(innodb db) onto tape drive, and propose the following solution/script: # delete old mysql dumps rm -r -r /backup/mysql mkdir /backup/mysql # Dump all mysql databases mysqldump --all-databases -single-transaction --

Re: Limit SET command to 2 decimal places

Hi, On Dec 14, 2007 1:02 PM, J Trahair <[EMAIL PROTECTED]> wrote: > Hi Everyone > > I have a database with an OrderItems table, containing (at least) 3 fields, > namely ExtendedPurchasePrice, CurrencyConversion and > ExtendedPurchasePriceSterling, all fields as doubles. > > I want to update Exte

best practice MySQl backup onto tape

Hi, I'm planing to do hot backup MySQL(innodb db) onto tape drive, and propose the following solution/script: # delete old mysql dumps rm -r -r /backup/mysql mkdir /backup/mysql # Dump all mysql databases mysqldump --all-databases -single-transaction --flush-logs > all_datab

Limit SET command to 2 decimal places

Hi Everyone I have a database with an OrderItems table, containing (at least) 3 fields, namely ExtendedPurchasePrice, CurrencyConversion and ExtendedPurchasePriceSterling, all fields as doubles. I want to update ExtendedPurchasePriceSterling for each row with the result of the calculation Ext

RE: before insert trigger

Not in MySQL 5.0. There is no error trapping mechanism to escape triggers as currently implemented. You are better off writing a stored procedure to do the INSERTs and have your application call the stored procedure. -Original Message- From: Ed Reed [mailto:[EMAIL PROTECTED] Sent: Thursd

Re: Weird behavior with date(null) and if

Baron Schwartz schrieb: > On Dec 13, 2007 4:18 PM, Daniel Mikic <[EMAIL PROTECTED]> wrote: > >> Baron Schwartz wrote: >> >> Hi, >> >> On Dec 13, 2007 3:53 PM, Daniel Mikic <[EMAIL PROTECTED]> wrote: >> >> >> Hi, i hit a weird behavior: >> >> select date(null); #result is null >> select if(dat