Hi,
1.0.4 seem to be case sensitive or something else is wrong, anyway when I
change SEQ_Appointment to SEQ_appointment in the ojb_hl_seq table I still
get the error. It will propbably be OK when I restart my server but I like
to do that at night and not in the middle of the day. Is there a way
Hi,
In my previous mail I said that it would probably be OK if I restart the
server. I made sure there is an entry SEQ_appointment but I still cannot
insert records due to this error. Any hints?
thanks,
Dennis
Hi jakob,
Ok, it is working with 1.0.4.
But if i want retreive the super class alone, a wrong SLQ
query is made, I have seen on the forum that is a bug. My
question is : do you know if this defect will be fixed on 1.0.5 ?
Best regards
Nicolas DELAHAYE
hi nicolas,
ojb just release 1.0.4. could
Hi,
I just moved to OJB 1.0.4. One thing I noticed is that it started
generating OUTER JOIN although I didn't specify it to do so. In my case
with ReportQuery with following columns:
String[] queryColumns = new String[] {
allChildren.addressLine1,
After some tests found out that OJB generates LEFT OUTER JOIN instead of
INNER JOIN in a 1:N relationship if both ends are same class.
Is that a planned functionality or a bug?
In my case I need 1:N relationship to be made from MyClass to Collection
of MyClasses... How can I force then OJB to
Hi Dirk,
Kessler, Dirk wrote:
There appears to be a change in behavior in the Database.makePersistent
method. In OJB 1.0RC7 the Database.makePersistent class would update the
primary key field of the object being persisted (autoincrement) even
before the transaction was committed (I.E. right
Dennis Bekkering wrote:
Armin,
It was the cache setting not the lazy loading.Fast as lightning again ;-)
Strange though that without caching the 2nd number of queries is less?
Indeed that's strange! Are you sure that no cache was used in your test
(e.g. enable logging for class
Hi Dennis,
Dennis Bekkering wrote:
Hi,
In my previous mail I said that it would probably be OK if I restart the
server. I made sure there is an entry SEQ_appointment but I still cannot
insert records due to this error. Any hints?
Did you note in release-notes (1.0.4) in section CHANGES that
excuse me for doing before reading;). I replaced the repository_internal and
it is OK now. Thanks!
2006/1/10, Armin Waibel [EMAIL PROTECTED]:
Hi Dennis,
Dennis Bekkering wrote:
Hi,
In my previous mail I said that it would probably be OK if I restart the
server. I made sure there is an
Hi folks,
I've put the 1.0.4 release into the maven repository. If all goes
well, it should be visible sometime tomorrow (if not earlier). Please
let me know whether it works (esp. the dependencies in the pom),
because I'm not a maven user myself, rather I've been strictly
following the release
10 matches
Mail list logo
