Of course, you will need to adjust these settings to fit your configuration (maybe different user credentials, server IP, etc.). But what if a product is removed after an order is created that references it SQL allows you to handle that as well. We know that the foreign keys disallow creation of orders that do not relate to any products. Add the new lines below (to adjust) for your PostgreSQL extra-connection: 4 Answers Sorted by: 34 Straight from the manual. The lines above should be already there with the appropriate values. 'autoload' => 'core/modules/pgsql/src/Driver/Database/pgsql/', 'namespace' => 'Drupal\\pgsql\\Driver\\Database\\pgsql', Now edit you Drupal site configuration file "settings.php" and add this database connection details: // Somewhere in your settings.php, you should have something like that: INSERT INTO people(name, date_of_birth, grade, tid) VALUES INSERT INTO teams(name, description) VALUES Then connect to your secondary new new PostgreSQL database "staff_db" with your account "pgother" and create tables: CREATE TABLE teams( Setup your secondary databaseĬonnect to your secondary PostgreSQL database with your "pgsql" account and create a new database: CREATE DATABASE staff_db OWNER pgother You can do it either using drush or by DELETEing all entries of cache_* tables of Drupal database. You may clear a couple of cache (container, config, discovery, router, plugin, menu.) and then rebuild the cache. ![]() It is very often a problem of cache not properly updated. It has the same effect as an unqualified DELETE on each table, but since it does not actually scan the tables it is faster. ![]() TRUNCATE quickly removes all rows from a set of tables. You may, from times to times, at the beginning, experiment WSOD (White Screen of Death). TRUNCATE is a PostgreSQL extension that provides a faster mechanism to remove all rows from a table.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |