Subject | Re: [ib-support] journalling |
---|---|
Author | Claudio Valderrama C. |
Post date | 2002-02-26T06:07:30Z |
""Jason Frey"" <jason_frey@...> wrote in message
news:001801c1bd95$119308b0$e65b0244@cx706785b...
anyone to go through a selectable stored procedure to retrieve data. The
fact that the proc is selectable doesn't stop it from writing to audit
tables. Of course, your users may notice some performance drain. And when it
comes to post, you should make you app post to a view or table, because the
procedure cannot be the subject of an update command.
Otherwise, use middleware and make sure nobody can bypass it.
C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing
news:001801c1bd95$119308b0$e65b0244@cx706785b...
>I can be done if you predefine the data that users can see, so you force
> Is there any sort of trigger akin to AFTER FETCH, or some such, for when a
> person just views a record?
> I know, probably a long shot, given the various ways to "view" a record
> (Joins, used in other triggers/SPs, etc). But, thought I'd throw the
> question out there, just in case.
anyone to go through a selectable stored procedure to retrieve data. The
fact that the proc is selectable doesn't stop it from writing to audit
tables. Of course, your users may notice some performance drain. And when it
comes to post, you should make you app post to a view or table, because the
procedure cannot be the subject of an update command.
Otherwise, use middleware and make sure nobody can bypass it.
C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing