Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Unless of course if you have <em>two</em> databases located on <em>two</em> different DB servers, why don't you simply create a table <code>articles</code> and a table <code>stock</code> referencing it. You could add the <em>shop</em> (ideally the <code>shop_id</code>) as an extra column of that latter. Something like that:</p> <pre><code>CREATE TABLE articles(id int primary key not null, name char(20) not null); CREATE TABLE stock(article_id int not null, shop ENUM('M', 'S') not null, qty int not null, FOREIGN KEY(article_id) REFERENCES articles(id), UNIQUE(article_id, shop)); </code></pre> <p>Please see <a href="http://sqlfiddle.com/#!2/e6eca/5" rel="nofollow">http://sqlfiddle.com/#!2/e6eca/5</a> for a live example.</p> <p>If you really need to restrict creation of items on table <code>articles</code> to <em>shop M</em> that could be achieved by creating different users for your DB (*user_m*, *user_s*) and using <code>REVOKE</code> and/or <code>GRANT</code> to setup the various access rights.</p> <hr> <p><strong>EDIT:</strong> If the two servers are on distant sites, you would probably be able to use <a href="http://dev.mysql.com/doc/refman/5.0/en/replication.html" rel="nofollow">MySQL replication</a> capabilities to keep one or many tables in sync between the two sites. This will require a network access between the two sites. As of myself, for obvious reasons, I would consider using a secure tunnel between the two sites. Finally you still probably have to set-up permissions at DB-level to only allow insert from one site and not the other. </p> <p>As a "poor's man" solution, you finally have the possibility to backup on regular basis the required tables from one server to update the tables on the second server. A combination of mysqldump + cronjob would be good starting point.</p> <p>As of myself, I would though push to <em>MySQL replication</em>. The setup is probably more complex. But this will perform better, scale better and have lower latency.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I keep two article tables synced, but keep stock separate
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSylvain Leroux
    1. USSylvain Leroux
    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. This table or related slice is empty.
    1. COThanks, Sylvain. I'm afraid that is not possible: both shops run their own local database, as we can't really rely on the communication between them. I only use replication to get the info in S updated as soon as possible.
      singulars
      1. PO
      1. USjcoppens
    2. CO@jcoppens By re-reading your question, I noticed than when you talking about replication you probably talking about "custom-made replication". But MySQL has its own replication capabilities that might be an interesting option in your very specific case.
      singulars
      1. PO
      1. USSylvain Leroux
    3. COI've added a note to the original post. I already replicate, with MySQL's mechanism, for the main articles table.
      singulars
      1. PO
      1. USjcoppens
 

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