creating a table from the application. is it Inefficient ?
posted 11 years ago
assuming i have upgraded my database with a create table statment. this statment is called from the program everytime the user is requested to do somthing.
question: is it inefficient to "create table" more than once just to make sure the table exist?
of course, if the table exist...I continue with insert/update/etc (thanks to try & catch) but the checking of the creation itself is it a significant time consuming (mind that the program is on a network).
Hi It could be better not to check Database if it is kinda busy database. I think you should create Table once . if you have to update your database often then it would be better to make the version of database persistent in some other file format . Best item is to check the Database status (weather updated or not)from a Properties file.
Even you can make a version table in your database and check the verion from it.