Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <ol> <li>Ship it on a DVD accompanying your product.</li> <li>Make it available for download from a website.</li> <li>If bandwidth allows, provide a web service and have all your users connect to your central database via the web service instead of having standalone instances of your data.</li> </ol> <p>Once you distribute data, it's more or less out of your control. You can do things like encode or encrypt it, but it's not a foolproof solution. The only real, sure-fire way to protect your data is to not give it out.</p> <p>That having been said, there are a few possibilities:</p> <ul> <li>Encrypt the database in some way. If the database isn't for reporting and doesn't need to have a lot of general queries run against it, you can encrypt at the row or field level. This will REALLY slow down the system, though.</li> <li>If using an embedded database, encrypt the entire file. This will significantly slow down startup and shutdown time for your app, though.</li> </ul> <p>Unfortunately, once you distribute your data, it's a losing battle to try to secure it. A better bet, if you can, is to provide a query web service so that your data are never archived en toto by a user - you just send them query results over the wire. You can adopt a user authentication strategy to verify that only legitimate users use the system, and maintain tighter control over your data that way.</p> <p><strong>EDIT</strong>: see my final paragraph. If you're distributing your data, you no longer have explicit control over who can come into possession of it, so any "control" of your data must be due to encryption or a similar protection. Unfortunately, you have to distribute a key at some point to the user (or the software the user's operating) in order to access the data. A sufficiently sophisticated user will then be capable of capturing the key and breaking your data protection. But, given that complete security is an impossibility once your data are in the hands of the user, you can give it your best effort by applying encryption. Your only two real options at that point are to encrypt data per row (or field?) or to encrypt the entire embedded database file.</p>
    singulars
    1. This table or related slice is empty.
    1. POBest way to ship 1GB of structured textual data used in my software?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDathan
    1. USDathan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBest way to ship 1GB of structured textual data used in my software?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI've edited my question. Please go through once.
      singulars
      1. PO
      1. USclaws
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload