On Thu, Mar 05, 2009 at 12:35:29PM +0100, Spitzer, Thomas scratched on the wall: > Hello, > > As already said, we plan to use the sqlite for the parameters of an > embedded system. > Triggers shall be used, to write the changes do the hardware drivers, > wherever necessary. > > Among the whole paramitration there are some "parameters" which are > actually reads to specific hardware addresses.
> Questions: > 1. Is it correct, that triggers on reading values (select) are not > supported? > 2. Any idea, for a workaround? As others have mentioned, the most straight forward idea is to just write a function that returns the requested data. Depending on how many parameters you're talking about, you might also consider a virtual table. Virtual tables are kind of the ultimate "trigger on select(and insert/update/delete)", in the sense that any operation on the table ends up calling your code to figure out what to do. You could define a two column virtual table with "name" and "value", for example. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Our opponent is an alien starship packed with atomic bombs. We have a protractor." "I'll go home and see if I can scrounge up a ruler and a piece of string." --from Anathem by Neal Stephenson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
