This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 77696 - [55cat] Better names for OneToMany
Summary: [55cat] Better names for OneToMany
Status: RESOLVED DUPLICATE of bug 98163
Alias: None
Product: javaee
Classification: Unclassified
Component: Persistence (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Andrei Badea
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-11 21:21 UTC by brviking
Modified: 2008-05-19 22:19 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description brviking 2006-06-11 21:21:58 UTC
[ JDK VERSION : 1.5.0_06 ]

Suppose following table:

create table Issue (
  IssueNo integer not null primary key,
  Subject varchar(100),
  Description varchar(4000),
  Reporter integer not null constraint fk_reporter referentes User (UserId),
  LastUpdateBy integer null constraint fk_lastUpdateBy references User (UserId)
)

Actually, perssitence from db generates fields

private Users users;
private Users users1;

for last two fields of the table. Better names is

private Users reporter;
private Users lastUpdateBy;

(using column name as name of the field, not the referenced table).
Comment 1 brviking 2006-06-11 22:13:19 UTC
Correcting subject: the problem appear on OneToMany mappings. ManyToOne and
OneToOne are ok.
Comment 2 Dongmei Cao 2008-05-19 22:19:08 UTC
This is a dup of issue 98163 requesting for better cmr names

*** This issue has been marked as a duplicate of 98163 ***