Okay, but then it does need a seperate script. I'm going to resolve 
this ticket; please open seperate tickets as appropriate for:



1. scripts that would work fine if the blank lines had comments. (all 
in one ticket as you can).



2. scripts that need custom oracle versions to work properly (one 
ticket per app would be great).



Thanks!

Yes it will be OK for SQLPLUS with default settings, but don't forget 
Oracle specific data types and DEFAULT notation. Should be written as 
this:



     task_private    NUMBER(16) DEFAULT 0 NOT NULL,

--

     PRIMARY KEY (task_id)

What I was thinking was that for the scripts for apps like Nag, we 
could do this:



     task_private    INT NOT NULL DEFAULT 0,

--

     PRIMARY KEY (task_id)



That make more sense?

Well any comments are accepted. If you comment out the blank lines 
_inside_ SQL

statements, all will work fine. The blank lines will be accepted 
outside of SQL statements also.

I've made the change to oracle_create.sql. I don't want to change 
other apps scripts to eliminate lines if possible, but I don't want to 
have to have oracle-specific scripts either - thus the question about 
comments. Let me know.

Will a line with a comment on it count as blank, or would that be accepted?

Platform: Apache1.3.31+php4.3.8+Oracle9.2.0.1



File horde/scripts/db/oracle_create.sql,v 1.6.

The table creation scripts for Oracle contain blanklines before

PRIMARY KEY clause.

The SQLPLUS utility on Oracle9.2 doesn't like this by default because 
the SQLBLANKLINES parameter defaults to OFF.



Suggest adding "set sqlblanklines on;" at the script start for 
seamless table creation.

Note: this issue is applicable for other applications, such as Turba, 
Whups etc.