Ok, I have fixed my versioning problems. I can access the new
PersistenceBroker methods and the code runs. To rule out any website related
sideeffects, and to get more info about what is happening, I have created a
separate test app and set debugging levels more verbose.
The test code looks like
On Wed, 14 Apr 2004, Stijn de Witt wrote:
Now I see the insert for address passing an id, which looks wrong to me
(since it is an auto-increment column), but it works ok. However, the
generated id is never fetched from the database, so it is no wonder that the
personId and addressId fields in
Hi Stijn,
Is it recommended to use mysql's auto-increment with OJB? If so, what
am I
doing wrong? If not, what other approach might you suggest?
hmm, it should work. Your code seems ok. In OJB junit test suite we have
one test using Identity column based PK fields. You can find this test
Hi Doug,
seems like a classloader problem. Do you have different ojb-jar files
(or source/classes + ojb-jar) in classpath?
regards,
Armin
Doug Poland wrote:
Hello,
I'm trying to learn OJB but am struggling getting a simple project to
run in Eclipse 2.1.3. I found what appears to be a good
Hi all,
I want to try JDO with OJB but I have some misunderstood.
I am not very clear about where to put the MetaData for the mapping ?
In the repository.xml or in the XXX.jdo ?
I look in the tutorial5 and I see that information for the mapping are
stored in the Product.jdo.
So should we put
Odd. Some notes...
Task.getClass().getName() works better as Class#toString isn't the
class name =(
Do you not get ANY objects back, or do you get a different object back
form the query?
Is the foreign key a primitive type by chance?
-Brian
On Apr 13, 2004, at 8:20 PM, Wil Hunt wrote:
Hey
Glad I can help =)
The sources etc (minus the jars) are posted as well, url is on a slide
toward the end.
-Brian
On Apr 13, 2004, at 7:28 PM, C Qualset wrote:
Thanks very much for posting the slides. It is a great place for a
newbie like me to start.
Ah, I missed the checkin message on that! Thank you!
-Brian
On Apr 13, 2004, at 5:20 PM, Oleg Nitz wrote:
On Tuesday 13 April 2004 15:17, Brian McCallister wrote:
Huh, the ODMG slower thing is interesting as Armin just reemed us all
out for letting the OTM get so much slower than ODMG ;-)
Have
I have a problem with this type of select. This is my code:
**
Criteria crit =3D new Criteria();
org.apache.ojb.broker.query.ReportQueryByCriteria query =3D new =
ReportQueryByCriteria(Estudiant.class, crit);
query.setColumns(new String[] { MAX(ID) });
Iterator iter2 =3D
Appear that latest CVS Head is assuming auto-update='false' as
auto-update='link'. Is this the correct behaviour? It should not be
auto-update='none'?
I've debugged OJB and seen this behaviour. I will need to fix all my
repository files from auto-update='false' to auto-update='none'?
Thanks
Just a stab at trying to help. Hopefully I have read your problem statement
correctly.
I'm using auto increment for a MS SQL Server 2000 DB. It needs rc6--but
that's just MS SQL Server.
OK. If you're having the DB assign the PK value, then you need an attribute
autoincrement=true and
You need both if you are using the JDORI plugin. It is annoying =(
The native JDO impl I am working on for OJB will allow you to just use
the OJB mappings as the .jdo files will only be used for (optional in
OJB but not for spec-compliant JDO) bytecode enhancement process. This
JDO impl is
Hi Carles,
Report Queries return an Iterator of Object[]
Object[] objs = iter2.next();
Integer max = objs[0];
Hope this helps,
Wally
-Original Message-
From: Carles Duque [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 7:54 AM
To: [EMAIL PROTECTED]
Subject: Select MAX
I
I think that when you make an object persistent, the persistence manager
automatically sets the objects pk according to the database.
Have you tried printing the department bean id after you committed the
transaction?
Pedro Salgado
-Original Message-
From: Philippe Guillard
Hi Glenn,
Thanks for your message. I had just completed converting the sequencemanager
to HighLow and setting autoincrement to ojb, and that seems to fix it,
however, I find this solution less elegant, because the sequencemanager is
ojb-specific and I would like to keep the base db model
Brian,
I _don't_ want to filter my queries. Can I give the native
implementation a try?
Would that be the CVS Head or would it be a different branch?
Thanks.
Charlie
Brian McCallister wrote:
You need both if you are using the JDORI plugin. It is annoying =(
The native JDO impl I am working
Hi Edson,
Edson Carlos Ericksson Richter wrote:
Appear that latest CVS Head is assuming auto-update='false' as
auto-update='link'. Is this the correct behaviour? It should not be
auto-update='none'?
I've debugged OJB and seen this behaviour. I will need to fix all my
repository files from
Nicolas Arni-Bloch wrote:
I have try to deal with LOB and OJB but they are a of documentation.
The oracle LOB are pointer to the value, therefor with JDBC you can not
make a classic insert. The procedure to insert a LOB as 3 phases :
1) insert a record with empty_blob() or empty_clob()
2) make
You will need CVS HEAD, correct -- also make sure you are comfy looking
around the sources to see what is implemented and not. I have tried to
throw OperationUnsupportedException(Not yet imeplemented!) when a
feature isn't actually implemented yet =)
This code is being actively written so it
Aye, readonly will do it! I had to look in the source code for
SequenceManagerNativeImpl to the extractIdentityColumnField() method. Try
it! You'll like it!
private FieldDescriptor extractIdentityColumnField(ClassDescriptor cld)
{
FieldDescriptor[] pkFields = cld.getPkFields();
Thanks Wally, really good...
The final code:
**
Criteria crit = new Criteria();
org.apache.ojb.broker.query.ReportQueryByCriteria query = new
ReportQueryByCriteria(Estudiant.class, crit);
query.setColumns(new String[] { MAX(ID) });
Iterator iter2 = broker.getReportQueryIteratorByQuery(query);
After going home last night and thinking about this over a beer, I realized
that either I was high yesterday, or my brain ceased to function properly.
The description I gave was not an accurate portrayal of the problem at hand.
(Though it would have had similar results if I HAD had the problem.)
I take it that if you close the app, and load it again then the task
appears?
If so, i'd guess it's down to caching. I had this problem, although i'd
assumed that this was a 'feature'.
After each insert do:
PersistenceBroker broker =
PersistenceBrokerFactory.defaultPersistenceBroker();
A programmer at my side found a problem when storing objects that have
collection with auto-update='true' or auto-update='link', with
proxy='true'. The problem appear be the following piece of
PerfistenceBrokerImpl.java:
private void storeAndLinkOneToMany(boolean linkOnly, Object obj,
Hi Edson,
many thaks!
The fix is now in CVS.
regards,
Armin
Edson Carlos Ericksson Richter wrote:
A programmer at my side found a problem when storing objects that have
collection with auto-update='true' or auto-update='link', with
proxy='true'. The problem appear be the following piece of
On Wednesday 14 April 2004 15:51, Brian McCallister wrote:
Have I missed something? Are there any new performance tests?
Armin emailed the -dev list a few days back =)
What was the subject? Still can't find.
-
To unsubscribe,
Hi Oleg,
try this
[OTM] Massive performance decrease between Feb and Apr version
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=6875
regards,
Armin
Oleg Nitz wrote:
On Wednesday 14 April 2004 15:51, Brian McCallister wrote:
Have I missed something? Are there any new performance
27 matches
Mail list logo
