F
Fernando Souza
Guest
To add to what Gus described. Running code that references any table in a database (including via dynamic programming) will cause the client to hold a shared schema lock for as long that program is running/active. Most schema changes are considered offline, that is, you can't have anyone running any code while you make the schema changes. The exception is if you are doing an online schema change, which only covers a very limited set of changes. You have to select the appropriate option when loading the .df and that will allow you to do the following while users are running code: - add a new table - add a new field to an existing table - add a new index For those 3 cases, existing r-code will continue to run (since 10.1C or so). Other schema changes that cause the table CRC to change will prevent r-code that access those tables to run and will need to be recompiled.
Continue reading...
Continue reading...