|
It is possible to have a collision, yes.
You would probably be best to use a domain variable as kind of transaction
flag: Set var on Make view Use view Drop view Set var off Then you can test to see if the var is on
and either deny the new request or adjust the name of the view. If you need this process to be industrial strength
the variable should be stored in the database and you should use transactions
to test/set it. I’ve done this procedure for a
once-a-minute cron that sends emails. I use a flag like this to prevent the
same email from being sent more than once. Alternatively, you can name your view “MYVIEW<@USERREFERENCE>”
and prevent user to use collisions. Robert -----Original Message----- hey guys, if in a .taf file, i have a dbms to
create a view, another to use a view, then another to drop the view, and the
view is named something constant like myview, is it possible to have a
collision? like have someone hit the dbms to
create a view but the view has already been created by another user but not yet
dropped? if so does anyone know a way around
this? Thanks! Alan ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf |
- Witango-Talk: views on the fly Alan Wolfe
- Re: Witango-Talk: views on the fly Robert Shubert
- Re: Witango-Talk: views on the fly John McGowan
- Re: Witango-Talk: views on the fly Eric Weidl
