;>> but the fact that it is not
>>> stable is a little disconcerting to me since I am writing something that
>>> will be in production before
>>> it is even gets into a release candidate stage.
>>>
>>> Any other ideas?
>>>
>&
ets into a release candidate stage.
>>
>> Any other ideas?
>>
>>
>>
>> - Original Message
>> From: Matt Kerr
>> To: user@cayenne.apache.org; Bret Gregory
>> Sent: Tuesday, August 25, 2009 10:55:15 PM
>> Subject: Re: Newbie Ques
I am biased, but I find 3.0M6 quite stable.
Personally, I find the 'development' labeling on apache.org misleading.
It's way more solid than that. (We've had it in production for quite
some time - on large internet site.)
If you're starting from scratch - I would recommend 3.x
There's been a lo
BTW, I'm writing something I expect to go into production in the
October time-frame. I'm using 3.0M6 and have every expectation that
it will work. Especially since I'm sticking to the "Classic" Cayenne
feature set, which is stable and has seen improvements in 3.x, too.
mrg
On Wed, Aug 26, 2009
t;
>
>
> - Original Message
> From: Matt Kerr
> To: user@cayenne.apache.org; Bret Gregory
> Sent: Tuesday, August 25, 2009 10:55:15 PM
> Subject: Re: Newbie Question: Mapping a Collection of Strings
>
> Hey Bret -
>
> Unless I'm missing - yes, this is right on th
Hi Brett,
You will have to map a Keyword class in both 2.0 and 3.0, and maybe
create a cover method converting a list of Keywords to a list of
Strings on the fly.
3.0 supports something called "flattened attributes", which is what
you describe, but only for to-one relationships.
Andrus
Question: Mapping a Collection of Strings
Hey Bret -
Unless I'm missing - yes, this is right on the mark for cayenne.
If you have an existing database, the easiest is to create a new model
and use Tools -> Re-engineer Databae Schema, ie
http://cayenne.apache.org/doc/reverse-
Hey Bret -
Unless I'm missing - yes, this is right on the mark for cayenne.
If you have an existing database, the easiest is to create a new model
and use Tools -> Re-engineer Databae Schema, ie
http://cayenne.apache.org/doc/reverse-engineer-database.html
Note- I find there a few quirks in t
I have a DB that looks something like this:
Product
-ProductId
-Description
Keyword
-ProductId
-Keyword
Where Product -> Keyword is 1:N and Keyword has a FK rel back to Product.
I would like the object model to look something like this:
Product
-(String) _description
-(List) _keywords
Is
