Hi Armin.
I imagined that I wasn't doing it properly.
Until now it looks going well, but I don't like it.
I hope to test it properly very soon and I'll tell you.
What I should do is to have 2 ojb.properties and 2
database-repository.xml.
I tried to do so, putting one in the ejbs directory, and
Hi,
we are trying to upgrade our OJB version from RC5 to 1.0.1.
We are using the ODMG API.
In RC5, when removing items from a collection of a write-locked
object, the transaction commit deleted the removed items from the
database. This does not seem happen any more in v1.0.1. All that is
sent to
Hi everbody,
We just discovered that Sybase (and Oracle), understand also the standard SQL outer-join syntax.
Since legacy Sybase Outer-Joins have several restrictions (that do not apply to ANSI outer joins) and deliver different results than the ANSI outer joins, I would like to know if
it is
Hi Armin, thanks for your response.
I think I have a bug in my code too... :)
I am using 1.0.0, should I upgrade?
I'd be happy to send you the full project, it contains a bunch of
persistence-capable classes and a single maven test case, of which I
have posted the code.
Here are things I wonder
Hi Stijn,
at the end of writing this mail I found that you are using inheritance
hierarchy to multiple joined tables for Candidate. The ODMG-api doesn't
work properly with this feature (PB-api does, sorry this was only noted
in 1.0.1 release-notes). Additionally you define in Person
Hi Armin,
Well I figured out what happens. In the rc5 application (which was made
some time ago) the repository-settings were:
auto-update=false
auto-delete=false
auto-retrieve=true
(just like in the rc7 application) but the big difference is that in the
r5 application when i changed a 1:1
Hi everbody,
We just discovered that Sybase (and Oracle), understand also the
standard SQL outer-join syntax.
Since legacy Sybase Outer-Joins have several restrictions (that do not
apply to ANSI outer joins) and deliver different results than the ANSI
outer joins, I would like to know if it is
Thanks for your message, it clears up a lot.
I guess I'll use the PB api then. Do you know if/when this will be fixed
for ODMG?
Thanks for your responses to all the little questions too. If have some
new in reaction to your answers, please read below...
Armin Waibel wrote:
Hi Stijn,
at the end
Hi
I have funny problem with OJB and Collections (m:n relations). Sample servlet code
(GET metgod):
//---
//adding roles
CMSRole admin = new CMSRole(CMS_ADMIN);
CMSRole author = new CMSRole(CMS_AUTHOR);
CMSRole developer = new
I haven't seen anyone ask this, but in my plan to migrate from OJB 0.9.9 to
1.01. I've run into a bit of a problem manipulating the cache, due to
changes in the caching between versions.
In several cases we use database views as beans, and whenever we update the
table behind the view we would
hi gerhard,
afterStore() is not called when using odmg (it is for pb-api !). i'm not an
odmg-expert, so i do not know if it's an error or if there should be a different
mechanism to remove those elements.
jakob
Gerhard Grosse schrieb:
Hi,
we are trying to upgrade our OJB version from RC5 to
Is this a bug? Or I am missing something
The following tests are failing:
Here is my snippet of repository xml:
field-descriptor id=3
name=user
column=USR
jdbc-type=VARCHAR
primarykey=false
nullable=true
hi gerhard,
i marked the removed object as deletable, then it worked:
tx.begin();
//*
tx.lock(fetchedGat, Transaction.WRITE);
// Remove collection object
tx.markDelete(fetchedGat.getCollectiblesC().remove(0));
hi ajitesh,
imo this is a rather old javadoc :(
the current one is like this:
/**
* Adds and equals (=) criteria,
* customer_id = 10034
*
* @param attribute The field name to be used
* @param value An object representing the value of the field
*/
you'd
All,
How can I do update statement updates changed columns only?
Ex: TABLE A (
IDNUMBER,
DESC VARCHAR,
CAT VARCHAR)
I need update only CAT field, but the code generate for p6spy is:
UPDATE A
SETDESC = '',
CAT= 'P'
WHERE ID = 1
[],
15 matches
Mail list logo