Re: drop table and locks

In article <8916@emory.mathcs.emory.edu> mm@ssf.pt (Manuel Monteiro) writes: > Hi there list, > > We have detected a problem when droping a table (temporary or not) or an > index in a database without transactions. > > When someone drops a Table or an Index, the program leaves a lock on the table. > > This is particulary serious when dropping a table, because the lock > remains on a table that no longer exists. > [4gl example program omitted] I ran your program with rds 4.1 against a 4.1 OnLine engine and was not able to see any problem. When the program prompted saying that there was a lock, I was able, using ISQL from a different user id, to select, insert and update rows in the table. I was also able to create an index xab on t(a,b) at this time. When the table had been dropped, an attempt to select produced message -211, the table is not in the database. At this time (while the program was prompting that "there is a lock in the dropped table") I was able to create a new table of the same name ("t"). This isn't definitive since you don't specify the products you are using: which engine (SE, turbo, online) at what version on what hardware platform; and which 4GL, RDS or compiled? Also, please make it clearer what you mean by "there is a lock on the table." Could you be specific about what SQL operation the other process attempts, and what SQL and ISAM error codes it receives as a result?