![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, Our product creates one table each every day to store data for a specific day. The tables created have identical columns. Whenever a new table is created, a view is created that includes all the underlying tables. If the view is queried from the interactive sql (dbisqlg)(select * from eg_event_view) and the client is kept open accidentally or unintentionally, we're unable to delete the view and create fresh view that includes new table created. The view deletion call just gets hung in the JDBC. Is there a way by which in interactive sql some options can be set so that, it does not created shared locks on the tables/views that are queried. Thanks, Krishna |
#3
| |||
| |||
|
|
Hi Krishna, DBISQL 11.0.0 includes an option to automatically release table locks. To enable it, open the Options window, click "SQL Anywhere" in the left pane, then check the "Automatically release database locks" box in the right pane. -- Chris Irie Sybase iAnywhere knazare (AT) bmc (DOT) com> wrote in message news:4a8a4ba0.16ee.1681692777 (AT) sybase (DOT) com... Hi, Our product creates one table each every day to store data for a specific day. The tables created have identical columns. Whenever a new table is created, a view is created that includes all the underlying tables. If the view is queried from the interactive sql (dbisqlg)(select * from eg_event_view) and the client is kept open accidentally or unintentionally, we're unable to delete the view and create fresh view that includes new table created. The view deletion call just gets hung in the JDBC. Is there a way by which in interactive sql some options can be set so that, it does not created shared locks on the tables/views that are queried. Thanks, Krishna |
![]() |
| Thread Tools | |
| Display Modes | |
| |