BareFeet wrote: > > I thought I saw syntax of some other SQL engines that > permit if/then or case/when type branching within a trigger, but I may > be mistaken. >
A case/when expression is just that an expression. It can appear any where an expression can be used. It can contain multiple sub-select statements, but it can't be used to select between insert, update, and delete statements. Some dialects of SQL support SQL procedures which could be used to do such things, but SQLite does not. > > Yes, although now I'm keen to see fixed the apparent huge overhead of > the inefficiency that Steve raised about using updatable views ;-) > Likewise, I think this is a very good optimization idea that should be implemented as soon as possible. I see he has created a ticket to get it on the radar at SQLite HQ. Dennis Cote _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
