Project

General

Profile

Bug #5489

Cleanup / reimplement merge DMO definitions

Added by Ovidiu Maxiniuc almost 3 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:

Related issues

Related to Database - Feature #4011: database/persistence layer performance improvements Closed

History

#1 Updated by Ovidiu Maxiniuc almost 3 years ago

  • Related to Feature #4011: database/persistence layer performance improvements added

#3 Updated by Ovidiu Maxiniuc almost 3 years ago

After dropping Hibernate from our libraries, the merge DMO definitions process is broken. In fact, it is probably dead code.

If I am not mistaken, this was used for gathering the whole set of DMOs when generating the final DDL. This included both DDL from previous partial conversion and from hand-written code.

Some aspects to be taken into consideration:
  • dmo_index.xml is gone;
  • the .hbm.xml are not generated at all as they are really not needed with new ORM, the information they contained is provided by annotations;
  • the 'partial' conversion and the new incremental conversion;
  • the ___Impl class are not generated any more, instead they are assembled dynamically, at runtime, for all databases;
  • generate_ddl.xml and generate_seq_ddl.xml, although still present in FWD's rule are not invoked. The generation of the DDL is performed using the DDLGeneratorWorker for permanent tables and TempTableHelper for temporary.

#4 Updated by Roger Borrello almost 2 years ago

Have there been other changes that have rendered this moot? I was just reading through a Redmine, and wanted to follow-up on some of the loose ends.

Also available in: Atom PDF