565 reputation
514
bio website
location
age
visits member for 3 years, 1 months
seen Sep 3 '13 at 18:09

Oct
8
awarded  Nice Question
Jul
11
awarded  Popular Question
May
28
awarded  Notable Question
Mar
22
awarded  Yearling
Sep
18
awarded  Notable Question
May
16
awarded  Popular Question
May
3
awarded  Nice Answer
Mar
22
awarded  Yearling
Mar
21
comment Should one use a separate database for application data and user data?
@GrandmasterB In this case it's a SQLite DB on a user's desktop. A parts database is perhaps a good example of the situation, but add in an inventory table that's FK'd on the parts table or something like that. I need to be able to push out updates to the parts table (the application data) on without affecting the user generated data (ie. the inventory data).
Mar
21
comment Should one use a separate database for application data and user data?
@JonRaynor Well, the tables are already separated, so the boundary already exists, it's just a matter of patch-ability. I'd have to update via a script that does a bunch of inserts, rather than be able to just copy over an updated database file.
Mar
20
comment Should one use a separate database for application data and user data?
@RobertHarvey - it's a single database per installation to a PC. I may need to be able to push out a global update to all users to add new application data occasionally. For purposes of exporting user data and importing it to another user's application, it is pretty essential that the application data PKIDs be identical across all machines.
Mar
20
comment Should one use a separate database for application data and user data?
@WinstonEwert - User data, although some of the user data may reference values from application data tables. I think that may be part of what's concerning me.. the possibility that somehow my updates may result in different key IDs to application data tables (though it really shouldn't if I'm doing the same operations on everyone's) and imports may go awry if so.
Mar
20
comment Should one use a separate database for application data and user data?
@DavidAndersson - On a user's PC.
Mar
20
comment Should one use a separate database for application data and user data?
the data is all tightly coupled.. aside from "leaf" tables, there are no tables which do not reference another table. The "it bothers me" aspect is more somewhere along the lines of being worried about somehow mangling user data with an update somehow, but I can't imagine how if I'm only inserting new data into application data tables. The IDs should never be changing of any of the data in those tables, so consistency shouldn't be an issue.. is this just paranoia..?
Mar
20
comment Should one use a separate database for application data and user data?
I wrote the first comment before your edit, but yes, XML is the clear choice to me for import/export. I'm curious though about your mentioning of the need to move the database - can you suggest to me an example of when I would need to move the application database and not the user data? I'm having a hard time wrapping my head around coming up with a specific example.
Mar
20
comment Should one use a separate database for application data and user data?
@WinstonEwert - no, the application is preloaded and should only be updated during a software update.
Mar
20
comment Should one use a separate database for application data and user data?
I believe the converse (or is it convex? I can never remember..) is more necessary for this particular application; the user needs the ability to export some of his data to give to another user of the application who can read it in. I don't foresee a need for needing to move the application data separately.
Mar
20
accepted Building a table (DataGridView) while keeping decoupled from Model
Mar
20
accepted Java/C# - When should AOT be considered if reverse engineering is a concern?
Mar
20
asked Should one use a separate database for application data and user data?