ditto here
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jonathan
Gibbons
Sent: Wednesday, February 27, 2002 3:34 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] Q : database and entity bean development
Hi,
Use a BMP code generator and then you
Hi,
Use a BMP code generator and then you can do anything you want. CMP is actually just
a code generator which hides the code. Now if CMP generated the code and then let
coders play with it... that would be good.
My LowRoad code generator is a BMP generator which does the thousands of line
Behalf Of Dain
Sundstrom
Sent: Tuesday, February 26, 2002 11:52 AM
To: David Goodwin
Cc: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Q : database and entity bean development
> Am i right in thinking that if i used BMP (Bean managed persistence) I
> would get around all my problems so far (e.g.
danch wrote:
> David Goodwin wrote:
>
>> Dain Sundstrom wrote:>>
>>
>>> If you do design your db first, don't try to use not null foreign
>>> keys or foreign keys in your primary key, as neither work yet.
>>>
>>> -dain
>>
>>
>>
>> Am i right in thinking that if i used BMP (Bean managed persiste
David Goodwin wrote:
> Dain Sundstrom wrote:>>
>> If you do design your db first, don't try to use not null foreign keys
>> or foreign keys in your primary key, as neither work yet.
>>
>> -dain
>
>
> Am i right in thinking that if i used BMP (Bean managed persistence) I
> would get around all
> Am i right in thinking that if i used BMP (Bean managed persistence) I
> would get around all my problems so far (e.g. I can't at the moment have
> foreign keys as part of the primary key etc) ?
Sure. When you get done writing a couple thousand lines of code to
manage a simple relationship,
Dain Sundstrom wrote:
> David,
>
> Build the beans first, as they are likely to change drastically during
> development. Then as your development winds down, lock down the exact
> db mapping.
>
> The only real negative to this approach is if you need some default data
> in your db for testin
David,
Build the beans first, as they are likely to change drastically during
development. Then as your development winds down, lock down the exact
db mapping.
The only real negative to this approach is if you need some default data
in your db for testing and you want to load this with a sql
