script update of DB linked field fails to update
Posted: Wed Sep 10, 2008 5:40 am
Hi all
Using v3 with SQLite DB and thought I'd try again using the QueryObjects. So have a bunch of fields which are linked to DB and set to update on edit. One of these fields is updated under script control but does not get updated in the DB. Any ideas why?
I'd prefer to fix these types of problems (if possible) than to continue to use workarounds (i.e. putting an "Update" button, etc).
On a related note, saving binary objects (e.g. pictures) should also be better handled. For example, I've read that it's best to base64encode/decode BLOBs before saving in the DB. But this assumes that a picture has been imported into an image object, rather than as a reference (using "set the filename .."). Surely in our DB library it would be easy to check for this and change the settings if necessary?
i.e. if the filename of an image object is set then read the image in, encode if necessary, before saving. And the reverse when reading?
Anyone have more info / comments?
cheers
Alan
Using v3 with SQLite DB and thought I'd try again using the QueryObjects. So have a bunch of fields which are linked to DB and set to update on edit. One of these fields is updated under script control but does not get updated in the DB. Any ideas why?
I'd prefer to fix these types of problems (if possible) than to continue to use workarounds (i.e. putting an "Update" button, etc).
On a related note, saving binary objects (e.g. pictures) should also be better handled. For example, I've read that it's best to base64encode/decode BLOBs before saving in the DB. But this assumes that a picture has been imported into an image object, rather than as a reference (using "set the filename .."). Surely in our DB library it would be easy to check for this and change the settings if necessary?
i.e. if the filename of an image object is set then read the image in, encode if necessary, before saving. And the reverse when reading?
Anyone have more info / comments?
cheers
Alan
