Quote:
Originally Posted by carlosag
basically you are saying that we should've click no in the dialog box when we first added the database??
|
Well, that all depends. If you click NO, then the IDE will leave the database alone, where it is (say it's in C:\temp) and the database will:
NOT appear in the project
NOT be copied out
NOT be included in an installer msi
MUST be used from C:\temp (the connection string is created with an absolute path)
That database might also belong to another app, be in use by that app, and suddenly your app will go making a mess in it. This might not actually be desirable!
Overall, the idea of software is that you have a nice clean version. You build, create a copy of all resources, mess them up etc, but when you come to release a final copy to your customer, you want them to start with a nice clean blank database, right?
So, say yes, set it to Copy if Newer, and everyone is happy!
Quote:
|
what's going to happen when you publish the app??
|
In terms of what? Your test data? Well you should always perform a CLEAN ALL which deletes all temp files, old versions etc. However, because you typically dont (or shouldnt) run your published version (publish is different to Debug or Release) the database within it should never accumulate any junk!
Quote:
|
or when you want to add more columns after the app is published??
|
when your app is out in the wild, you either:
Provide a new database with the new schema
Copy their data into it
or
Use DLL commands such as ALTER TABLE t ADD newCol VARCHAR2(100)
Back-fill them with data (maybe)