Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Simple way for a small company: dump your database to SQL and add it to your repository. Then every time you change something, add the changes in the dump file. </p> <p>You can then use diff to see changes between versions, not to mention have comments explaining your changes. This will also make you virtually immune to MySQL upgrades. </p> <p>The one downside I've seen to this is that you have to remember to manually add the SQL to your dumpfile. You can train yourself to always remember, but be careful if you work with others. Missing an update could be a pain later on. </p> <p>This could be mitigated by creating some elaborate script to do it for you when submitting to subversion but it's a bit much for a one man show.</p> <p><strong>Edit:</strong> In the year that's gone by since this answer, I've had to implement a versioning scheme for MySQL for a small team. Manually adding each change was seen as a cumbersome solution, much like it was mentioned in the comments, so we went with dumping the database and adding that file to version control. </p> <p>What we found was that test data was ending up in the dump and was making it quite difficult to figure out what had changed. This could be solved by dumping the schema only, but this was impossible for our projects since our applications depended on certain data in the database to function. Eventually we returned to manually adding changes to the database dump. </p> <p>Not only was this the simplest solution, but it also solved certain issues that some versions of MySQL have with exporting/importing. Normally we would have to dump the development database, remove any test data, log entries, etc, remove/change certain names where applicable and only then be able to create the production database. By manually adding changes we could control exactly what would end up in production, a little at a time, so that in the end everything was ready and moving to the production environment was as painless as possible.</p>
    singulars
    1. This table or related slice is empty.
    1. POStarting with versioning mysql schemata without overkill. Good solutions?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USManos Dilaverakis
    1. USManos Dilaverakis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. COThis way you can easily get an old version up and running quickly.
      singulars
      1. PO
      1. USrunfalk
    2. COwhy not just dump every time after a change? maybe a batch file that dumps the schema and auto-commits (just this file)? the manual step makes it just harder, imho
      singulars
      1. PO
      1. USstefs
    3. CO@Schnalle - good point. The way I see it, it's up to personal preference. Personally I'm willing to do the manual part just so I can simply right-click on the dump file and use options like "show differences" and "blame" with Tortoise.
      singulars
      1. PO
      1. USManos Dilaverakis
 

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