Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Enhancement Requests and Suggestions » View Thread |
Messages 1 to 2 of 2 total |
Formatting of SQL-text after Reverse-Engineering |
Wed, Mar 5 2008 11:14 AM | Permanent Link |
Uli Becker | Small wish: When reverse-engineering a database, the SQL-statements of SP's get an
additional indent of 22 blanks. Original: --------------------------------------------------------------------------------- BEGIN DECLARE Result CURSOR WITH RETURN FOR Stmt; if StatusID > 2 then /*BG-Posten*/ PREPARE Stmt FROM Generated Script: --------------------------------------------------------------------------------- EXECUTE IMMEDIATE 'CREATE PROCEDURE "ShowPosten" (IN "RechnungenID" INTEGER, IN "StatusID" INTEGER) BEGIN DECLARE Result CURSOR WITH RETURN FOR Stmt; if StatusID > 2 then /*BG-Posten*/ PREPARE Stmt FROM Result after executing the Script: --------------------------------------------------------------------------------- BEGIN DECLARE Result CURSOR WITH RETURN FOR Stmt; if StatusID > 2 then /*BG-Posten*/ PREPARE Stmt FROM It just would be nice to keep the formatting. Regards Uli |
Thu, Mar 6 2008 5:02 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Uli,
<< Small wish: When reverse-engineering a database, the SQL-statements of SP's get an additional indent of 22 blanks. >> Yes, this was intentional to make the formatting of the creation script be more readable. However, I forgot that this would cause the created script to be improperly formatted. I'll fix this for the 1.09 release. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Friday, March 29, 2024 at 03:30 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |