| Subject | Re: [firebird-support] isql metadata extraction problems |
|---|---|
| Author | Helen Borrie |
| Post date | 2009-02-26T00:07:47Z |
At 12:06 AM 21/02/2009, you wrote:
On Windows w. v.2.1.1 I did notice that the isql output was inserting an arbitrary number of blank lines ( 1 or more) before the semicolon, apparently only for views. Haven't tried 2.1.2 on Windows yet.
I don't use EMS DBExport so can't comment. IB_SQL's metadata extract tool uses '^' (default, but configurable) as the terminator from start to finish, not chopping and changing back and forth as the isql tool does. It outputs a script that can be processed in either isql's script processor or its own. It doesn't seem to be making any mistakes with either 2.1.1 or 2.1.2.
./heLen
>Hi,Can't reproduce the problem on Linux with v.2.1.2 using isql with either -x or -a switches.
>
>I've noticed that metadata extracted with either isql or EMS DBExport
>has some problems when replaying it back to a new database (v2.1.2).
>
>Specifically, I get some views not terminating in a semi-colon.
On Windows w. v.2.1.1 I did notice that the isql output was inserting an arbitrary number of blank lines ( 1 or more) before the semicolon, apparently only for views. Haven't tried 2.1.2 on Windows yet.
I don't use EMS DBExport so can't comment. IB_SQL's metadata extract tool uses '^' (default, but configurable) as the terminator from start to finish, not chopping and changing back and forth as the isql tool does. It outputs a script that can be processed in either isql's script processor or its own. It doesn't seem to be making any mistakes with either 2.1.1 or 2.1.2.
>I canNot clear what you mean here. CREATE VIEW doesn't require a semi-colon at all if it's presented as an ordinary DSQL statement. The semi-colon terminator for statements is an isql-thing.
>create views ending in two semicolons (but not more) and the server
>does not complain. Any ideas?
./heLen