Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm just taking a stab at this, so be warned :) The DatabaseManager class, which is used whenever you call DB, has and extend method. Here's the <a href="https://github.com/laravel/framework/blob/master/src/Illuminate/Database/DatabaseManager.php#L160">link to the source</a>. The DB::connection() method should return an instance of <a href="https://github.com/laravel/framework/blob/master/src/Illuminate/Database/Connection.php#L95">Illuminate\Database\Connection</a>. From all this, I would create a new user connection as follows:</p> <pre><code>$user = Auth::user(); DB::extend($user-&gt;username, function() use ($user) { // $pdo = new PDO(); set this up how you see fit return new Illuminate\Database\Connection($pdo, $user-&gt;databaseName, $tablePrefix); }); </code></pre> <p>Personally, I would add a new method to each user, User::databaseConnection(), and call that when I extend the DatabaseManager.</p> <pre><code>DB::extend($user-&gt;username, function() use ($user) { return $user-&gt;databaseConnection(); }); </code></pre> <p>Through out your application you should be able to call a registered user's connection via:</p> <pre><code>DB::connection(Auth::user()-&gt;username); </code></pre> <p><strong>Update</strong></p> <p>Depending on how often and when you'd be calling the tenant connection, you may want to use the IOC container.</p> <pre><code>App::bind('tenantDB', function() { return DB::connection(Auth::user()-&gt;username); }); App::make('tenantDB')-&gt;insert(...); </code></pre> <p>I forgot about migrations and seeding. For migrations, you can set the file path</p> <pre><code>php artisan migrate:make foo --path=app/migrations </code></pre> <p>So if you use the Config class to set the default database or DB::setDefaultConnection($username), I'd assume all migrations and seeding will be done for the current connection. When that process if complete you can switch back to you main database.</p> <p><strong>Update 2</strong></p> <p>The laravel developers are amazing and I should have definitely got the urge to check this out sooner than later. You can do migrations and seed on any database connection you've created. </p> <pre><code>artisan migrate --database='userConnectionName' artisan db:seed --database='userConnectionName' </code></pre> <p>Looking at Barry's answer, that is probably a good deal simpler than extending the DatabaseManager.</p> <p>If you want to see all the options for these commands just run:</p> <pre><code>artisan help migrate artisan help db:seed </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POLaravel 4: Multiple Tenant Application, each tenant it's own database and one global database
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBlessing
    1. USBlessing
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POLaravel 4: Multiple Tenant Application, each tenant it's own database and one global database
      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. VTAcceptedByOriginator
    1. COThat is a pretty nice solution. Can you clarify one thing for me? How would each migration run for each tenant? Like i said there is a just one set of application files and tenants are not hardcoded in any way. All tenants must run the current version of the application so they also have migrate accordingly.
      singulars
      1. PO
      1. USVictor Gutierrez
    2. COSo I think I just found you a better solution. The migrate command does have a database option so `php artisan migrate --database='userConnectionName'` should work. For the seeding, you may still have to change the default connection. I'd say you have a couple options though: (1) write a custom command that does the seeding or (2) put in a feature request for a --database option for the seeding command.
      singulars
      1. PO
      1. USBlessing
    3. COso scratch my last comment about seeding. the seeding also has a --database option. `artisan db:seed --database='userConnectionName'`. These laravel developers are awesome!
      singulars
      1. PO
      1. USBlessing
 

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