I'm seeing a deflate trigger being called when you do a save() even
if the column that has the trigger has not had a value set, nor does
it have a default value. This is not a huge issue, i don't really
have a problem with it, was just an observation really.
I'm also seeing an inflate trigger being called when you do a get on
a field that you just set. I.e. the value you are getting back should
not need to be inflated because it hasn't touched the database yet.
$foo->bar('foobar'); ## no inflate/deflate done yet.
print $foo->bar; ## triggers an inflate.
$foo->save; ## triggers a deflate.
This causes some problems if you are encrypting your field with your
triggers. When you do the second step there, it is triggering the
inflate, which would typically be a decrypt type method, which in
this particular case will try to decrypt something that is not
encrypted. Then when the save comes along, it is encrypting the now
garbled value.
However, it all works perfectly if you save directly after setting
the field with the trigger.
regards,
Danial Pearce
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Rose-db-object mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rose-db-object
