Hi Tom, [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] wrote: > > after a catalogextract all outstream FILE 'testdb.catalog' DDL > > I corrected some statements, which were wrong > - comment on user without any apostrophe > - some commanddelimiter where they should not be ( and so on ... ) > > Then I tried a catalogload all instream FILE 'testdb.catalog' . > > But without success : > > catalogload has modified the testdb.catalog file in a weird way: > > Some statements have now a command delimiter on their line > > e.g. > > CREATE VIEW testview1 AS SELECT a,b,c FROM tab1 // > GRANT SELECT ON VIEW testview1 TO ... > > this '//' at end of the commandline causes an error in catalogload > > My questions : > 1. Why is the catalogfile modified by catalogload ? > Actually, the Loader does not change the catalog file during a CATALOGLOAD as it opens the file for reading only. It is indeed weird that the file has changed after a load. Would it be possible for you to provide me with the 3 files - the one the Loader generated during CATALOGEXTRACT (with wrong commands), the one you used to CATALOGLOAD (with your corrections), and the one changed after the load? I have no clue why the Loader should change the file.
> 2. Is it possible to change the commanddelimiter from '//' to perhaps > semicolon like in other databases ? > ( I think there is a multiline mode in loadercli which > can interpret > semicolon as commanddelimiter but this doesn't affect > the 'real' db-commands in the catalogfile ) > It is not possible for the processing of a CATALOGEXTRACT command. So the Loader will always generate a command delimiter '//' during CATALOGEXTRACT. Regards, Steffen -- Steffen Schildberg MaxDB Team SAP Labs Berlin -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
