Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have to wonder why you're even bothering with a database at all, when the layer you've added on top to chunk, store, retrieve and reassemble would work just as well on a well-defined filesystem structure. MySQL wants all of its data on a <em>single</em> volume, so it's not a case of adding another drive whenever you feel like it, and replication of large amounts of binary data is going to be cripplingly slow as the binary logs will end up duplicating the amount of data you need to store.</p> <p>The simplest approach is often the best one. Storing this in the filesystem directly is probably the best way to do it. If you need to keep an index of what's stored where, maybe you'd use a database like MySQL, but there's many ways to accomplish this same task. The more low-tech, the better. For example, don't rule out <a href="http://www.sqlite.org/" rel="nofollow">SQLite</a> because an embedded database performs very well under light read and write load, and has the advantage of being "just a file" when it comes to backing up and restoring.</p> <p>That being said, what you're doing sounds suspiciously similar to <a href="http://code.google.com/p/leveldb/" rel="nofollow">LevelDB</a>, so before you commit to your approach, you'd have to see how it's significantly different than a key-value document store of that variety.</p>
    singulars
    1. This table or related slice is empty.
    1. POStoring large files / binary data in a mysql database: when is it ok?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UStadman
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POStoring large files / binary data in a mysql database: when is it ok?
      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. VTAcceptedByOriginator
    1. COThanks for your answer, you raise some interesting ideas. The project already uses a WAMP environment for various other tasks, so I thought I may as well utilise what was already there. Also I had a look at LevelDB and it looks great, but I don't think it's quite right for my needs on this occasion: "It does not have a relational data model, it does not support SQL queries, and it has no support for indexes". I can't help thinking that will cause me more problems. The reason for using the database in the first place was just that I had already set up the infrastructure for the other sync items
      singulars
      1. PO
      1. USAlfie
    2. COYour point about the binary logs is quite alarming though, so I think I will consider moving towards a 'proper' file system - do you think it would be ok to still use the database sync to transfer, before assembling to binary on the other side (and then deleting binary from the database)? Using the database allows me to keep an accurate track of which blocks of data have and haven't been received (there could be a possibility they won't be received in order)
      singulars
      1. PO
      1. USAlfie
    3. CODatabases are very good at storing well-defined relational data. They are awful at storing large amounts of arbitrary binary data. What you might use is a hybrid, a LevelDB data store with an RDBMS index built on top. LevelDB is great at storing enormous amounts of data, and can be replicated using standard tools like `rsync`.
      singulars
      1. PO
      1. UStadman
 

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