Hello,
How can I safely get all objects locked by a transaction using ODMG or broker API?
I need this because I want to remove all objects locked by a transaction from the
cache. Something like this:
.
Iterator lockedObjects=getLockedObjects(transaction);
while
Hello,
I am new to OJB and in the process of evaluating it for use on our project. So far I
am very impressed and looking forward to using it in production.
To that end, I have written my own sequence manager. It appears to work (records are
created correctly with GUIDs correctly generated).
RE: problems with batch-mode=trueSeems it works for me when I tried
following
1) batch-mode="true" in repository
2) start transaction before setting the batch mode
broker.beginTransaction();
broker.serviceConnectionManager().setBatchMode(true);
3) I tried this on delete. There were no e
Hi,
I am a newbie in OJB and an now trying the OJB using the ODMG API. I run the
tutorials on the OJB website successfully. But when I am trying one of my
own project, I was stuck in two problems,
1)
for the query string, if I use "select p from Project where companyCode = $1
and billingCode= $2
hi,
scarab seems to have moved to
http://issues.apache.org/scarab/servlet/scarab/
jakob
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
In the JDO specification, we can find :
public java.lang.Object newObjectIdInstance(java.lang.Class pcClass,
java.lang.String str)
This method returns an object id instance corresponding to the Class and
String arguments. The String argument might h
Yes, I've done all the tests, and really doesn't work.
If someone need to use 1:1 optional (or 1:0..1), cannot use proxy. But it's
not a lose performance scenario (at least for me), since it's 1:0..1 only...
If someone could double check it, please do... It's a boring bug that can
affect others try
Hi all,
i m trying to store an object A wich have a list of A element, when i try
that it works first time and after i got this exception
org.apache.ojb.broker.PersistenceBrokerException:
java.lang.StringIndexOutOfBoundsException: String index out of range: -2
at
org.apache.ojb.broker.core.Persi
Charles,
Ok sorry to rag on you. I know all about stupid decisions that are out of my hands I
doubt there is anyone who doesn't. Have a nice day.
Troy
-Original Message-
From: Charles Anthony [mailto:[EMAIL PROTECTED]
Sent: October 27, 2003 10:51 AM
To: 'OJB Users List'
Subject: OT Cra
Hi,
I am well aware that my email signature is
a) Unwieldy
b) Ugly
c) Technically dodgy
d) A pain in the backside.
It is also questionable whether it has any legal significance whatsoever - I
am pretty sure it is totaly useless outside the UK.
However, I am unable to change it.
It is appende
Charles or whoever owns that weird signature,
This is a little of topic but I find your signature is a little strange. Email is
traveling across a public medium so if it is unencrypted it is effectively public
domain viewable by anybody sniffing the net (regardless of what laws may exist). Plus
Armin
Thanks -- don't suppose you could grab me a CVS head could you if you get
the chance...
Thanks
Mark
-Original Message-
From: Armin Waibel [mailto:[EMAIL PROTECTED]
Sent: 27 October 2003 12:50
To: OJB Users List
Subject: Re: Auto incremented primary key and extents
Hi Mark,
M
Hi Mark,
Mark Rowell wrote:
Sorry
After looking at SequenceManaherHelper I know that the max id of sequence
for extent is not...
More on the batch mode stuff -- I onlt just turned it on and got these
problems. RC4 has been working
Prior to setting batch-mode="true" in the configuration.
hmm, AFAI
Hello,
> -Original Message-
> From: Christophe.Demarey [mailto:[EMAIL PROTECTED]
> I correct my repository definition (remove the table attribut from
> PersonBaseImpl descriptor) but I still get an exception.
> Any idea about it ?
>
> jav
Sorry
After looking at SequenceManaherHelper I know that the max id of sequence
for extent is not...
More on the batch mode stuff -- I onlt just turned it on and got these
problems. RC4 has been working
Prior to setting batch-mode="true" in the configuration.
-Original Message-
From: Mar
Armin
No the only thing I changed was OJB.properties.
One thing is that this problem happened during a run of my application where
some batch mode=true stuff
Was used. Would this have an impact?
Is the sequence max id still stored in OJB_HL_SEQ?
Regards
Mark
-Original Message-
From: A
Hi Mark,
> But as a follow on the extents are more than one level deep -- would
> this
> have an impact?
No should not. Have a look in
SequenceManagerHelper#getMaxForExtent
> unique Over all tables in the extent? Have I misconfigured OJB on
upgrading
> to RC4?
Did you change metadata on upgrading
Hi,
Charles Anthony wrote:
Hi,
Hello,
OK! It is a bit clearer for me, thanks.
Each time I want to use a broker I should do:
broker = PersistenceBrokerFactory.defaultPersistenceBroker();
//I use the broker
broker.close();
Yes, this is the way it should be done.
Is it better to do this EACH
Hi,
>
> Hello,
>
> OK! It is a bit clearer for me, thanks.
> Each time I want to use a broker I should do:
>
> broker = PersistenceBrokerFactory.defaultPersistenceBroker();
> //I use the broker
> broker.close();
Yes, this is the way it should be done.
> Is it better to do this EACH time I u
Hello,
OK! It is a bit clearer for me, thanks.
Each time I want to use a broker I should do:
broker = PersistenceBrokerFactory.defaultPersistenceBroker();
//I use the broker
broker.close();
Is it better to do this EACH time I use the broker or ask for a broker one time (when
the application sta
Sorry
But as a follow on the extents are more than one level deep -- would this
have an impact?
Regards,
Mark Rowell
-Original Message-
From: Mark Rowell [mailto:[EMAIL PROTECTED]
Sent: 27 October 2003 11:30
To: '[EMAIL PROTECTED]'
Subject: Auto incremented primary key and extents
Hi
Hi
I have an extent over 8 classes (and 8 corresponding tables) and I have
noticed that primary keys
are now not unique over all tables -- e.g. when I store and instances of 2
different classes
In different "leaves" of the extent I get the same ID in both tables. In RC1
I the autogenerated IDs wer
Hi,
at line 27, you should repeat lines 9-13.
At line 10 PersistenceBrokerFactory.defaultPersistenceBroker() asks the pool
for a broker, creating one *if* *necessary*.
broker.close releases some resources from the broker, and returns the
broker to the pool.
In other words, after you close the
Hello Thomas,
Is there a way to check how many instances are contained in the pool?
You can find an example below.
You create a broker instance in line 10, right?
You use the broker instance first time in line 19. After this use you close() the
instance.
But the problem is if you do the close()
Is it possible to combine functionality of EnhancedOQLQuery and Query?
I want to choose whether I need to get collection or iterator as a result of
OQL query. I want to use OQL as a basis to look up my objects, but some time
I need iterator. And I don't want to mix use of EnhancedOQLQuery and Qu
Thanks a lot Gerhard !
We all use ODMG, do we all have used lock(Write) and not
Database.makePersistent().
But if you tell me that we have to lock for an update bedfore any
modification it is clearer for me and explain why we have this behavious.
Thank you very much !!
-Message d'origine-
Andy
I found this as well but I have taken the extra step of prechecking which of
my objects exist so rather
Than doing a broker.store(object) I can call the store method that tells OJB
to update or insert -- stops
OJB querying to see if object exists. Must admit it does seem strange
though...
Ma
Hi Emmanuel,
AFAIK it shouldn't matter when you acquire a lock for new objects.
(Although it might affect the order of SQL statements during commit).
Btw, for new objects you can also use Database.makePersistent(), which
imo makes the intention of inserting a new object clearer.
For objects to up
On Monday 27 October 2003 00:25, Antonio Gallardo wrote:
> Oleg Nitz dijo:
> > On Sunday 26 October 2003 23:12, Antonio Gallardo wrote:
> >> Can this work with JDO?
> >
> > Yes, this is done at the PB level, therefore works for ODMG, OTM and
> > JDO.
>
> I tried it, and it works:
>
> proxy-prefetc
P6SPY ?
It's dead easy to use; p6SPY is a "wrapper" jdbc driver.
a) Ensure p6spy.jar is in the classpath, as well as the
b) find spy.properties in the OJB distribution - it's about somewhere. Copy
it, and place it on the classpath - actually, with the version of p6spy
distributed with OJB, we've
Could any one give me a hand on this one ?
Patrick Reyes
- Forwarded by Patrick Reyes/CDS/CG/CAPITAL on 10/27/2003 08:22 AM
-
Patrick Reyes
Hi Clay,
I think there is a consensus among the developers that we will have an
additional RC5. RC5 will be the codefreezes base for 1.0.
I think we need some more more work to reach a codefreeze state, at
least some weeks. There is no scheduled date for it.
For the time being I recommend to us
32 matches
Mail list logo
