Hi Andrew
As far as I can tell exposing the PK does not stop cayenne from
allocating them, but the trick might be the PK Generation strategy
(defined in the DbEntity). We are using 'default' strategy, no problems
at all.
Also you can use SQLTemplate query when the PK column was not exposed,
j
Hello;
There is probably a simple answer to this.
I am trying to use the following EJBQL to get the PK;
String queryS = "SELECT o."+XYZDataObject.ID_PROPERTY+" FROM
"+XYZDataObject.class.getSimpleName()+" o WHERE
o."+XYZDataObject.MODIFY_TIMESTAMP_PROPERTY+" > ?1";
From this I can mak
On May 3, 2010, at 3:56 PM, Borut Bolčina wrote:
I am looking forward to this configuration merging feature - if that
is what
you mean.
No. Merging configurations is a separate feature from getting rid of
singletons.
So, my-cayenne.xml can only include node B and not both nodes as
thi
I am looking forward to this configuration merging feature - if that is what
you mean. Is there some draft document about what you want to do?
-Borut
2010/5/3 Andrus Adamchik
> Just to add some perspective (and hopefully not to confuse things further),
> our direction in Cayenne 3.1 is towards
Thanks,
So, my-cayenne.xml can only include node B and not both nodes as this new
functionality only needs access to database B.
Is that correct?
-Borut
2010/5/3 Andrus Adamchik
>
> On May 3, 2010, at 3:12 PM, Borut Bolčina wrote:
>
> There will be cayenne.xml (with node A) and
>> my-cayenn
Just to add some perspective (and hopefully not to confuse things
further), our direction in Cayenne 3.1 is towards scenario #2, and
getting rid of #1 completely. This way a user decides where his
Cayenne stack (or multiple Cayenne stacks) is stored and how it is
accessed.
Andrus
On May
On May 3, 2010, at 3:12 PM, Borut Bolčina wrote:
There will be cayenne.xml (with node A) and
my-cayenne.xml (with node A and B) on the classpath. Is that why?
Yes.
I am not sure how to initialize.
#1 is created implicitly when you call
DataContext.createDataContext(). That's the one ret
Thanks for quick response,
Why 2 configuration instances? There will be cayenne.xml (with node A) and
my-cayenne.xml (with node A and B) on the classpath. Is that why? Would it
be more convenient if my-cayenne.xml only consist of node B?
I am not sure how to initialize.
-Borut
2010/5/3 Andrus
"Default" refers to a "default domain" within a single configuration
instance. You will be working with 2 configuration instances, so both
will have a "default domain". This also means that your old code can
stay unchanged, while the new application won't be able to use a
static method for
Hello,
Our old large web application uses one database and there are a large number
of DataContext.createDataContext(); statements all over the web application
itself and jars it depends on.
Now there is a need to access another database. Currently the Configuration
gets initialized with the firs
10 matches
Mail list logo
