Ticket #3 (closed task: fixed)

Opened 2 years ago

Last modified 2 years ago

Fix deleteByFk method

Reported by: chous Owned by: chous
Priority: normal Milestone: A-law algorithm (QueryJ 0.7)
Component: QueryJ Version: trunk
Keywords: templates Cc:
Include in GanttChart: yes Depends on: 2,18,19
Due to assign (leave blank to use ticket's creation date): 2006/07/23 Due to close: 2006/08/31

Description

The delete method of RDB implementations of the DAOs tries to delete all entities depending on it. In other words, it simplifies the deletion on cascade of a graph of dependant entities.

Currently, such logic is commented out in the templates, since it contains errors. The purpose of this ticket is, obviously, to fix such errors.

Change History

Changed 2 years ago by chous

  • status changed from new to assigned

The foreign keys the DAO template is aware of seem ok, but the code always use source table information instead of referring tables. As an example, A -> B <- C

BDAO.delete(bpk) {
  bdao.deleteByBPk(bpk); // should be adao.deleteByBpk(bpk);
  bdao.deleteByBPK(bpk); // should be cdao.deleteByBpk(bpk);
  // delete B by bpk...
}

Changed 2 years ago by chous

  • dependencies changed from 2 to 2,3

Changed 2 years ago by chous

  • dependencies changed from 2,3 to 2,18

Changed 2 years ago by chous

  • dependencies changed from 2,18 to 2,18,19

Changed 2 years ago by chous

  • status changed from assigned to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.