It would be great, when the run script function would allow SQL comments in/for/between (probably multiple) SQL-statements (respectively would parse them off).

There is no database interface such as phpMyAdmin for postgresql and the phpPgAdmin project on sourceforge seems to be dead... And the the task of creating tables/indexes/sequences for new modules would be much easier/faster/simpler in this case: simply paste the supplyed sql code into the run-script-form and run it. Here filestore.pgsql, for example:

-- translated by Rene Laederach (mussi@snoop.alphanet.ch)
BEGIN;
CREATE TABLE filestore (
  nid INT NOT NULL DEFAULT '0',
...
);
--
-- Sequences for table IF NOT EXISTS FSTORE_UPLOAD
--
CREATE SEQUENCE fstore_upload_;
CREATE TABLE  fstore_upload (
  upid INT DEFAULT nextval('if not exists fstore_upload_'),
...
);
--
-- Indexes for table IF NOT EXISTS FSTORE_UPLOAD
--
CREATE INDEX timestamp_fstore_upload_index ON fstore_upload (timestamp);
--
-- Sequences for table IF NOT EXISTS FSTORE_UPLOAD
--
COMMIT;

Comments

jeremy’s picture

Do you get an error when you paste in and run a script that has comments? I don't, using MySQL - it simply ignores the comments, which is what I would expect. (The only way I can get an error is if I have a trailing comment -- but even this doesn't hurt anything, the tables are still created.)

jeremy’s picture

Assigned: Unassigned » jeremy
Status: Closed (won't fix) » Fixed

SQL comments are now filtered when a script is run from the remote client.

Anonymous’s picture

Anonymous’s picture

jeremy’s picture

Status: Fixed » Closed (fixed)

Manually closing, the project module doesn't seem to do this automatically anymore.