Stored Procedures and Systables
Hello, Informix Dynamic Server Version 7.31.UC2A We want to call stored procedures with the following syntax : select sp_name(param) from systables where tabid=1; (procedures always return one value, we don't want to use 'execute procedure') All our applications are designed to "set isolation to dirty read". Do you think that there is a risk of lock on systables ??? Is there any other potential problem with using systables in this context ? Or is it better to create a dummy table with one row (like DUAL in Ora...)? Thanks in advance for your advices or remarks. Ben
System tables have row locking and this cannot be changed. I dont think there would be any problem with ur query. savio Henry Benoit <Benoit.Henry@Galvalange.lu> wrote in message news:8t1fct$mo5$1@news.xmission.com... > > > Hello, > > > Informix Dynamic Server Version 7.31.UC2A > > We want to call stored procedures with the following syntax : > select sp_name(param) from systables where tabid=1; > (procedures always return one value, we don't want to use 'execute > procedure') > > All our applications are designed to "set isolation to dirty read". > > Do you think that there is a risk of lock on systables ??? > Is there any other potential problem with using systables in this context ? > > Or is it better to create a dummy table with one row (like DUAL in Ora...)? > > Thanks in advance for your advices or remarks. > > Ben >
Hi Henry. For this isolation and for this type of query there is no reasons to worry about locking, but I think it is the good practice to make dummy table ( ala dual in Oracle ). Good luck. Sergey. Henry Benoit <Benoit.Henry@Galvalange.lu> ''''' ' ''''''''':8t1fct$mo5$1@news.xmission.com... > > > Hello, > > > Informix Dynamic Server Version 7.31.UC2A > > We want to call stored procedures with the following syntax : > select sp_name(param) from systables where tabid=1; > (procedures always return one value, we don't want to use 'execute > procedure') > > All our applications are designed to "set isolation to dirty read". > > Do you think that there is a risk of lock on systables ??? > Is there any other potential problem with using systables in this context ? > > Or is it better to create a dummy table with one row (like DUAL in Ora...)? > > Thanks in advance for your advices or remarks. > > Ben >