0001487: Many problems in Generating Oracle DDL - Tickets.CaseTalk

ID	Project	Category	View Status	Date Submitted	Last Update

0001487	CaseTalk Modeler	Generation (SQL, XML, etc)	public	2017-09-29 15:58	2022-01-10 20:40

Reporter	Stephan Volkmann	Assigned To	BCP Software
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Platform	Intel	OS	Windows	OS Version	7
Product Version	8.26
Target Version	8.27	Fixed in Version	8.27

Summary	0001487: Many problems in Generating Oracle DDL
Description	I found 4 errors/feature wishes in generating an Oracle DDL Script. Here is a list of what i found yet: 1. Problem/Improvement: Very much unnecessary Comments. There are so many empty comment sections in my model, but every empty one is kept in the ddl script. For every Table for each attribute there is [Comment] [Definition]. This may be deleted for better reading, and for focusing on the important comments. Example: /* TABLE AUFTRAG_EIGENSPANNUNGSANALYSE * [Comment] * [Definition] * Bearbeitungszustand der Proben: [Comment] * [Definition] * Charge der Proben: [Comment] * [Definition] * Haerte der Proben: [Comment] * [Definition] * Werkstoff der Proben: [Comment] * [Definition] etc. 2. Problem/Error: The SQL Command "COMMENT ON COLUMN" has an error in the syntax: Example: The wrong one: COMMENT ON COLUMN "AUFTRAG_EIGENSPANNUNGSANALYSE"."AUFTRAGSNR_SONDERMESSAUFTRAG" IS ''' The correct one would be: COMMENT ON COLUMN "AUFTRAG_EIGENSPANNUNGSANALYSE"."AUFTRAGSNR_SONDERMESSAUFTRAG" IS ''; The correction is only in the last syntax sign: ''' must be ''; 3. Problem/Feature: This is a combination of problem 1 and 2. The comments in the FCO-IM model are not connected with the "Comment on Column" or "Comment on table" command. Example: In my model: Fertigungsmaterial: [Comment] Dieser Fakt beschreibt, welches Material als Endprodukt im Fertigungsauftrag gefertigt werden soll. But in the script it is empty, and only in the comment section of the table: COMMENT ON COLUMN "FERTIGUNGSAUFTRAG"."FERTIGUNGSMATERIAL" IS ''' Solution a): Comment everything in the table. This would be very easy to handle, but the documentation in the database is not the best. Solution b): Connect Comments from facts, label types and object types to the ones in the database and comment them into the columns. 4. Problem/Feature: No examples are added into the database. This is a feature i would like to have, but i think this needs the most implementation effort in this ticket. Maybe you or I add a new ticket only for this problem. I don´t know it, but i think in the other scripts there is also no adding of examples to the generated database. Many text, sorry for that. But i just want to help improving the software :)
Steps To Reproduce	1. Open Project and repository 2. Transform model with GLR 3. Generate model with Oracle DDL Script Generator
Additional Information	Working with the Pre-Release-Version 8.26 Education Version
Tags	No tags attached.

CaseTalk Edition

Stephan Volkmann 2017-09-29 15:58 reporter	ForBCPRawModel_GLR_Oracle.SQL (64,284 bytes)

Stephan Volkmann 2017-09-29 16:04 reporter ~0001015	Oh, and i have another suggestion: When generating an oracle ddl, the table names, column names and keys may be only 30 characters long. The Table and Column Names are getting cutted correctly, but the primary keys and foreign keys are getting too large by adding the PK1_ or FK23_ to the name. Example: Label Type: THISLABELNAMEISTOOLONGBUTGETSCUTTEDCORRECTLY Cutted Column: THISLABELNAMEISTOOLONGBUTGETSC (30 Chars, okay) But then the PK1_ gets added --> PK1_ THISLABELNAMEISTOOLONGBUTGETSC --> >30 chars --> Error in script. Solution may be, that the Name gets cutted again after adding the PKs or FKs.

BCP Software 2017-11-06 16:46 administrator ~0001022 Last edited: 2017-11-06 22:08	1) Fixed. 2) Fixed. 3) is related to 0001493 4) Fixed. + MaxLengthID is fixed

BCP Software 2022-01-10 20:40 administrator ~0003314	Closing automatically, stayed too long in resolved state. Feel free to re-open with additional information if you think the issue is not resolved.

Date Modified	Username	Field	Change
2017-09-29 15:58	Stephan Volkmann	New Issue
2017-09-29 15:58	Stephan Volkmann	File Added: ForBCPRawModel_GLR_Oracle.SQL
2017-09-29 16:04	Stephan Volkmann	Note Added: 0001015
2017-11-06 15:57	BCP Software	Assigned To	=> BCP Software
2017-11-06 15:57	BCP Software	Status	new => assigned
2017-11-06 15:57	BCP Software	Target Version	=> 8.27
2017-11-06 16:46	BCP Software	Note Added: 0001022
2017-11-06 22:00	BCP Software	Note Edited: 0001022
2017-11-06 22:04	BCP Software	Note Edited: 0001022
2017-11-06 22:06	BCP Software	Note Edited: 0001022
2017-11-06 22:07	BCP Software	Product Version	8.25 => 8.26
2017-11-06 22:08	BCP Software	Relationship added	related to 0001493
2017-11-06 22:08	BCP Software	Note Edited: 0001022
2017-11-06 22:09	BCP Software	Status	assigned => resolved
2017-11-06 22:09	BCP Software	Resolution	open => fixed
2017-11-06 22:09	BCP Software	Fixed in Version	=> 8.27
2022-01-10 20:40	BCP Software	Note Added: 0003314
2022-01-10 20:40	BCP Software	Status	resolved => closed