StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I would suggest:</p> <ul> <li>Many-to-many: User <-> Conversation. A <code>User</code> can have many <code>Conversation</code>s, a <code>Conversation</code> consists of two or more <code>User</code>s</li> <li>One-to-many: User <-> Message. A <code>Message</code> belongs to one <code>User</code>. A <code>User</code> has many <code>Message</code>s</li> <li>One-to-many: Message <-> Conversation. A <code>Message</code> belongs to one <code>Conversation</code>. A <code>Conversation</code> has many <code>Message</code>s.</li> </ul> <p>This will give you following SQL structure (only attributes interesting for the relationships listed):</p> <pre><code>users: id messages: id | user_id | conversation_id conversations: id conversations_users: conversation_id | user_id </code></pre> <p>Think about conversations like chat rooms, its basically one shared collection of messages between a couple of users.</p> <p>In Laravel, possible Eloquent models would look like this:</p> <pre><code>class User extends Eloquent { public function conversations() { return $this->belongsToMany('Conversation'); } public function messages() { return $this->hasMany('Message'); // not as relevant, because these are all messages across conversations } } class Message extends Eloquent { public function user() { return $this->belongsTo('User'); } public function conversation() { return $this->belongsTo('Conversation'); } } class Conversation extends Eloquent { public function messages() { return $this->hasMany('Message'); } public function users() { return $this->belongsToMany('User'); } } // Users conversations $conversations = User::find(1)->conversations; foreach($conversations as $conversation) { // All members of conversation $members = $conversation->users; // All messages of conversation $messages = $conversation->messages; } </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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