On 8 Sep 2011, at 16:23, Chris Tate-Davies wrote:
Hello. I want to know if there is a special way I can access all the data in
the NEW/OLD data?
I realise I can access it by referencing NEW.fieldname but I want to
serialise the NEW object so I can save as a string. Is this possible or do
Thanks,
I kinda guessed that, but I'm not sure how to pass the OLD object to it
as MySQL cannot handle a rowset datatype.
Has anyone had any experience with this? Not sure where to start or how
to proceed.
Chris
On 13/09/11 07:40, Luis Motta Campos wrote:
On 8 Sep 2011, at 16:23, Chris
Hi,
Just quick reading your email, forgive me if I'm mistaken
what about serializing using *concat(old.f1,'|||',old.f2,'|||',old.f3)
('|||' = any separator that works for you)*
and deserialize inside the function?
does this make any sense to you?
Cheers
Claudio
2011/9/13 Chris Tate-Davies
I could do that, but I was hoping I wouldn't have to specify the
individual fields, and just pass the collection for parsing.
If I were to add any fields I would have to re-write the trigger which
is something I was trying to avoid.
On 13/09/11 09:53, Claudio Nanni wrote:
Hi,
Just quick
Hello
I have upgraded our backup server from mysql 5.0.77 to mysql 5.5.15. We are
using bacula as backup software, and all the info from backups is stored in a
mysql database. Today I have upgraded from mysql 5.0 to 5.5 using IUS
repository RPMS and with mysql_upgrade procedure, no problem so
I would recommend to go for a 15K rpm SSD raid-10 to keep the mysql data and
add the Barracuda file format with innodb file per table settings, 3 to 4 GB
of innodb buffer pool depending the ratio of myisam v/s innodb in your db.
Check the current stats and reduce the tmp and heap table size to a
Thanks for correcting me in the disk stats Singer, A typo error of SSD
instead of SAS 15k rpm.
Compression may not increase the memory requirements :
To minimize I/O and to reduce the need to uncompress a page, at times the
buffer pool contains both the compressed and uncompressed form of a
