Issue status update for http://drupal.org/node/25792 Post a follow up: http://drupal.org/project/comments/add/25792 Project: Drupal Version: cvs Component: postgresql database Category: tasks Priority: normal Assigned to: Anonymous Reported by: Smirnov Updated by: Cvbge Status: patch (code needs review) I like the patch, but IMO it needs to wait till http://drupal.org/node/26091 gets in Cvbge Previous comments: ------------------------------------------------------------------------ Sun, 26 Jun 2005 17:41:57 +0000 : Smirnov Attachment: http://drupal.org/files/issues/INSTALL.txt.oldnew.patch (4.39 KB) Although installing Drupal with PostgreSQL is rather straight forward, there are a few stumbling blocks (needing to load a language into the database and not using the public schema, as well as there being zero instructions): I have added instructions to /INSTALL.txt/ on how to load up the SQL scheme into PostgreSQL, and I have edited /database/database.pgsql/ so that it is easy to install drupal into any schema. As a result, users can now for example install Drupal into database drupal, schema drupal (with the functions in public). This means they could use different modules for different schemas if they wanted to. The instructions include: * Creating a database with /createdb/ * Loading up plpgsql language with /createlang/ * Inserting all the SQL data into the schema of choice * Changing /$db_prefix/ to reflect the schema ------------------------------------------------------------------------ Sun, 26 Jun 2005 17:42:50 +0000 : Smirnov Attachment: http://drupal.org/files/issues/database.pgsql.oldnew.patch (588 bytes) Attached the /database/database.pgsql/ patch ------------------------------------------------------------------------ Thu, 30 Jun 2005 16:11:52 +0000 : Smirnov Attachment: http://drupal.org/files/issues/INSTALL.txt.patch(install only) (4.48 KB) Updated INSTALL.txt against HEAD, also made it so the instructions pertain to installing to the "public" schema by default (and left a notice on there for people to edit database.pgsql if they need to do otherwise). The previous patches can now be safely ignored (esp. since they were for 4.6.1).