hi,
i am currently using cayenne with jndi resources. i use the cayenne-modeler as
a fallback as discribed here:
http://cwiki.apache.org/CAYDOC/using-jndi.html
which works fine till yesterday, where cayenne told me, that it cant find any
resources. in the end i deleted and recreated all
Hallo,
in our application we loose sometimes the reference to a mandatory foreign
object (not null, foreign key)
Our object relation are
Export Container - products
product - client
product - image
product - state
The problem occurs in our exporter process. It works like
Begin Transaction
Hallo Andrus,
now it works! Thank you for your helpful answers - not only this time
:-) I like the cayenne community ...
Is this easier in another version 1.2.1 ?
No. But it is fairly easy as it is.
Sorry for this question, it was very easy. I though I have to create
cayenne from source,
Hello,
I have been working some with Hibernate, and while I like a lot of what it
has to offer, but I am constantly frustrated with things that would be a no
brainier sql query, that takes hours if not days to try in shoehorn into
their paradigm. Here is a scenario that you cannot do in
Making a getStatusName() and even a setStatusName() is fine for
conveniently getting the status name (and not needing a local
statusName instance variable), but if you need to use statusName in a
query, that won't do what you want -- you still need to specify the
relationships. Also, you had
Yeah, the known issue is HSQLDB lock not being cleaned on abnormal
app termination of the modeler. Right now the only solution is the
one you described - close everything and delete all db[1..9]+.* and
db.lck files. Going forward we need to switch to some other DB like
derby or just start
I wonder if that's another consequence of this bug:
http://issues.apache.org/cayenne/browse/CAY-724
I implemented a fix that works in my application, but I still don't
fully understand the underlying cause of it. Still it looks like a
suspect here too. Anyways, here is a patched 1.2 jar
Yeah - creating a separate entity for Status and a simple one-to-many
relationship between Project and Status'es should solve the problem:
Project
String projectName
Status status
Status
String statusName
List projects
While you (Terry - the original poster) may want to choose
Terry,
Just noticed that according to your message, status_table has an FK
to project... Wouldn't you want the opposite if a project has just
one status? (other than that what others and myself suggested in this
thread is still correct).
projects_table
That much is true ... but ...
it would be nice if it was possible to describe
these things in the repository.
I've actualy created a database that holds this additional informations
and a little more like a meaningful names for attributes
and entities, and made a web-Interface using Googles
I would it do in the Andrus-Style ...
but it seems, as if the idea of terry is a freetext-status,
that is continous changed during the lifecycle of a project.
I wonder why this information is not placed directly in the project-table.
2006/12/21, Andrus Adamchik [EMAIL PROTECTED]:
Terry,
Just
11 matches
Mail list logo
