SQL connection
URL?
Thanks,
Andrus
On Mar 26, 2008, at 10:44 AM, Alexander Lamb wrote:
Hello List,
We have an application, deployed successfully with Tapestry 5.0.11
and Cayenne 3.0M3 on Tomcat 6 with MySQL 5.0.
Everything is fine until the point where a long period of
inactivity has pa
rformQuery(DataContext.java:
1320)
at
ch
.rodano
.studies
.services
.StudySession
.getRunningTotalPatientsByMonthForRegistryCenters(StudySession.java:466)
etc...
Thanks for any idea!
Alex
--
Alexander Lamb
Founding Associate
RODANOTECH Sàrl
4 ch. de la Tour de Champel
1206 Geneva
Switzerland
s means you'll have to physically convert the time,
not just apply the time zone offset.)
Maybe someone else will correct me if I'm wrong on this, but that is
the first approach I would try.
/dev/mrg
On Tue, Feb 26, 2008 at 8:25 AM, Alexander Lamb (dev)
<[EMAIL PROTECTED]> wrote:
M
Maybe I can rephrase the question: does Cayenne do any kind of
transformation when storing Date objects in TIMESTAMP fields?
If so, how can I control this?
Thanks,
Alex
Le 25 févr. 08 à 16:17, Alexander Lamb a écrit :
Hello,
Using Cayenne 3.0M3, MySQL 5.
I have a field which is a
Works fine, thanks! (my lack of Java knowledge)
Le 26 févr. 08 à 14:08, Andrus Adamchik a écrit :
On Feb 26, 2008, at 3:04 PM, Alexander Lamb (dev) wrote:
e.getCause() will give me an InvocationTargetException.
Sorry, I should've been more explicit. You need to unwra
System.out.println("* CAN'T DELETE INVOICE: " +
e.getMessage());
_session.getDataContext().rollbackChanges();
}
e.getCause() will give me an InvocationTargetException.
Alex
Le 26 févr. 08 à 10:56, Andrus Adamchik a écrit :
On
Hello List,
I want to prevent a delete of an object if certain attributes have
certain values (e.g. do not delete an invoice which has already been
sent).
I registered the callback in the Modeler. Works fine.
I do my test in the callback function I defined, it works fine.
Except that to "
the
formated value and not the actual date value).
How can I solve this problem?
Thanks,
Alex
--
Alexander Lamb
Founding Associate
RODANOTECH Sàrl
4 ch. de la Tour de Champel
1206 Geneva
Switzerland
Tel: 022 347 77 37
Fax: 022 347 77 38
http://www.rodanotech.ch
I am not mistaken your conversion pattern "[%p] %c{1} %m%n" does
not match the output, so it is very likely that some other
dependency and/or container trigger Log4J initialization prior to
your code being executed.
Andrus
On Feb 6, 2008, at 11:57 AM, Alexander Lamb (dev) wrote:
//cayenne.apache.org/doc/guide-to-30-features.html
(search for "logging" on this page).
Andrus
On Feb 5, 2008, at 6:32 PM, Kevin Menard wrote:
How are you bootstrapping your log4j configuration? I have
something like
the following before creating a DC:
org
.apache
.log4j
Hello List,
I don't seem to be able to stop Cayenne log all the SQL (3.0M2 or M3).
I have the following in my log4j.properties, but it doesn't seem to be
taken into account!
log4j.category.org.apache.cayenne.access.QueryLogger = WARN
log4j.category.org.apache.cayenne.conf = WARN
log4j.catego
://issues.apache.org/cayenne/browse/CAY-921
Andrus
On Feb 5, 2008, at 1:21 PM, Alexander Lamb (dev) wrote:
More info:
What happened is that we have class hierarchies in our models. With
M2, it works. With M3, it doesn't. What is also curious is that the
interface in the Modeler of M3
since reverting to an M2 version of our models and running the exact
same code with M2 works.
Alex
Le 5 févr. 08 à 12:05, Alexander Lamb (dev) a écrit :
Ok, I will try.
Maybe the model but I maybe did something stupid: I opened the
models with the M3 modeler then saved them. Still the
between M2 and M3 ? In other
words, can I continue to work with M3 modeler whatever version M2 or
M3 of Cayenne I am using?
Thanks,
Alex
Le 5 févr. 08 à 10:13, Andrus Adamchik a écrit :
On Feb 5, 2008, at 11:02 AM, Alexander Lamb (dev) wrote:
Caused by: java.lang.NullPointerException
at
Hello List,
I have a crash with M3 that I didn't have with M2. I updated the
models (I have two models), cleaned everything, rebuilt.
Upon first commit I get the following crash.
I am not doing anything special. Just inserting a record then saving.
Several queries worked perfectly well bef
no example for formatting them.
Thanks,
Alex
--
Alexander Lamb
[EMAIL PROTECTED]
the number of roles... Indeed, doing "addAll"
will first fire the to-many which was just created before adding the
objects...
The only way to avoid that initial fetch is to do:
tml.setObjectList(roles)
then continue with the writePropertyDirectly.
Alex
Le 15 nov. 07 à 10:45, Alexande
afraid I don't know anything about JPA, but it probably means in
the future some kind of interface in the modeler to be able to specify
those prefetches?
Thanks!
Alex
Andrus
On Nov 14, 2007, at 9:33 AM, Alexander Lamb (dev) wrote:
Well, yes it is possible up to a point.
Usually
way to the model?
Now, it would still be cool if we could have batch faulting for the
odd places where we didn't set up the prefetching.
Alex
Le 14 nov. 07 à 14:45, Andrus Adamchik a écrit :
Can you use prefetching instead? You got a list of users vis some
sort of query - just add
Hello list,
Again, about my performance issues.
To avoid thow round trips to fetch to-one relationships, we found a
temporary solution but it doens't seem quite perfect.
We override the get-to-many relationship in the following way:
@SuppressWarnings("unchecked")
public List getRoles () {
Hello list,
One thing is killing performance of our application: it is the
resolving of individual to-one faults in lists.
For example, we can have 200 roles each refering to a person.
When we loop through the roles, for each role where we do a
role.getPerson() there will be a return trip
This is great news, especially with the callbacks enabled!
Now, a question:
We have 3 apps in production using Cayenne 2.0.3, 2 with Tapestry 4.1
and one with Tapestry 5.
We are currently migrating the Tapestry 4.1 / Cayenne 2.0.3 to
Tapestry 5 and expect to go live around January (end of
Andrus,
It now works (or at least, it goes past the problem I had).
Indeed, entityResolver was null.
Initializing correctly the DataContext made it work. Maybe adding an
Exception in Cayenne warning of a null entity resolver (and telling
how to initialize the DataContext) could help?
We
ndrus
On Aug 31, 2007, at 6:15 PM, Alexander Lamb (dev) wrote:
Initially, it was a static method to fetch a Patient from the
primary key (give the DataContext, the String, returns the Patient
or null).
Since whatever I was doing would crash Cayenne, I simply tried to
do fetch all patients:
it was is just test code you were trying
to get to work. :-)
Exactly... in desperation, you end up trying many different things!
/dev/mrg
On 8/31/07, Alexander Lamb (dev) <[EMAIL PROTECTED]> wrote:
Initially, it was a static method to fetch a Patient from the primary
key (give the
text
(Patient.java:30)
is in your stack trace? What does that method do?
Thanks,
/dev/mrg
On 8/31/07, Alexander Lamb (dev) <[EMAIL PROTECTED]> wrote:
Hello list,
We are experimenting a Cayenne crash and wondering how to get
around it.
Here is the place of the crash:
java.lang.N
Hello list,
We are experimenting a Cayenne crash and wondering how to get around it.
Here is the place of the crash:
java.lang.NullPointerException
at org.apache.cayenne.query.BaseQueryMetadata.resolve
(BaseQueryMetadata.java:97)
at org.apache.cayenne.query.SelectQuery.getMetaData(SelectQuer
Java 5 only ( currently we are in production on Java 6 with Cayenne 2
and Tapestry 4.1 and migrating to Tapestry 5 which is Java 5 only :-)
Le 7 août 07 à 14:54, Michael Gentry a écrit :
[ ] Java 1.4 support
[X] Java 5 support
Given that a big change in Cayenne 3.0 is JPA, which requires Ja
Well, although it works, I still have a small problem.
When you do a "setAnObject" even if it does "magically" handle the
"addTo", it does so without calling the public "addToMyList" function.
This means I can't add some logic to the addTo function (I need to
perform some calculation each t
ct.addToMyRelation(mySecondObject)" is
already done for you.
This is why you're seeing two copies -- you're effectively calling
the
addToMyRelationship twice.
On 6/19/07, Alexander Lamb (dev) <[EMAIL PROTECTED]> wrote:
> Hello list,
>
> It looks like &quo
Hello list,
It looks like "myFirstObject.addToMyRelation(mySecondObject)" does
not check if mySecondObject is already in the relationship. Is that
correct?
If so, here is my problem.
I know that I can simply do:
mySecondObject.setTheObject(myFirstObject)
and then once saved, somehow the
y().getCenters());
>
>Andrus
>
>
>On May 24, 2007, at 12:36 PM, Alexander Lamb wrote:
>
>> Thanks Andrus, however, I am not doing relationship management in
>> that case.
>> Actually, I do NOT want to remove the center from the selected
>> country.
>&
#x27;t been a big deal as
>relationship management is better done via special methods.
>
>Andrus
>
>
>On May 24, 2007, at 10:54 AM, Alexander Lamb wrote:
>> Hello list,
>>
>> I am fetching a "List" of objects (a too many relationship).
>&
Hello list,
I am fetching a "List" of objects (a too many relationship).
Then in a loop, I am removing some objects:
List rcs = getRegistry().getRegistryCenters();
List centers = getSelectedCountry().getCenters();
for(RegistryCenter rc:rcs)
{
/cayenne/browse/CAY-712
Andrus
On Jan 21, 2007, at 11:10 PM, Alexander Lamb (dev) wrote:
Well, it might be me... having trouble with a class hierarchy. So
first I'll check that, then I'll be back with the
validateForInsert :-)
On Jan 21, 2007, at 6:49 PM, Alexander Lamb (dev) wrot
Well, it might be me... having trouble with a class hierarchy. So
first I'll check that, then I'll be back with the validateForInsert :-)
On Jan 21, 2007, at 6:49 PM, Alexander Lamb (dev) wrote:
Hello, me again!
Are you certain it is possible to handle fetches and cr
t 12:07 AM, Alexander Lamb (dev) wrote:
Hello list,
I am currently using Cayenne 2.0.
I read it was possible to modify objects during a
validateForInsert or validateForSave call (e.g. not the same as
old WebObjects).
What about creating a new object and inserting it in the
DataContext? W
37 matches
Mail list logo
