You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to create databases we'll need to use Doctrine's DBAL iirc, or at the very least Laravel's Schema stuff but I don't think that supported database creation.
It's feasible that we may end up linking databases to users and adding audit logs of the creation in future, so it should be its own class. Something like (new Servidor\Database())->create($name); which would be called from the Database API controller as well as from Sites during creation.
The text was updated successfully, but these errors were encountered:
Add basic database listing
Adds a basic (but filterable) table with a list of databases so the Databases item in the main sidebar menu finally has a purpose.
To get the list we add a new Database class that wraps Doctrine's DBAL which can eventually also be used to list tables etc.
This also sets up the ground work for #146.
Adds the ability to create a database (assuming it doesn't exist) by
typing its name in the search box and pressing enter. Couldn't really
be much simpler than that! Tested, too... Kinda.
Closes#146.
In order to create databases we'll need to use Doctrine's DBAL iirc, or at the very least Laravel's Schema stuff but I don't think that supported database creation.
It's feasible that we may end up linking databases to users and adding audit logs of the creation in future, so it should be its own class. Something like
(new Servidor\Database())->create($name);
which would be called from the Database API controller as well as from Sites during creation.The text was updated successfully, but these errors were encountered: