oliver.matz | 1 Sep 2003 10:03
Picon
Favicon

RE: new committers

Hello,

> -----Original Message-----

> Both Brian and Oliver received at least 3 positive votes and no veto.
> So I am happy to announce that Brian and Oliver now have 
> committer status.
> 
> Welcome on board!

Thank you very much.  I am looking forward to helping to improve OJB.

Olli
Stefan Bodewig | 1 Sep 2003 09:42
Picon
Favicon
Gravatar

Re: new committers

On Sun, 31 Aug 2003, Thomas Mahler <thma32 <at> web.de> wrote:

> Brian and Oliver, to set up the CVS access ASAP please tell me if
> the account names
> 
> brianmcc
> oliverm
> 
> would be OK for you or if you prefer something else.

in addition both should sign (and send in) the Contributor License
Agreement[1] form as this seems to have become a prerequisite to
account creation recently.

Cheers

        Stefan

Footnotes: 
[1]  http://incubator.apache.org/forms/ASF_Contributor_License_2_form.pdf
Thomas Mahler | 1 Sep 2003 12:04
Picon

Re: new committers

thanks Stefan for this hint.

Olli and Brian please sign this agreement and fax it back to the apache 
office.

Thomas

Stefan Bodewig wrote:
> On Sun, 31 Aug 2003, Thomas Mahler <thma32 <at> web.de> wrote:
> 
> 
>>Brian and Oliver, to set up the CVS access ASAP please tell me if
>>the account names
>>
>>brianmcc
>>oliverm
>>
>>would be OK for you or if you prefer something else.
> 
> 
> in addition both should sign (and send in) the Contributor License
> Agreement[1] form as this seems to have become a prerequisite to
> account creation recently.
> 
> Cheers
> 
>         Stefan
> 
> Footnotes: 
> [1]  http://incubator.apache.org/forms/ASF_Contributor_License_2_form.pdf
(Continue reading)

oliver.matz | 1 Sep 2003 13:18
Picon
Favicon

RE: new committers

Hello,

> -----Original Message-----

> Olli and Brian please sign this agreement and fax it back to 
> the apache 
> office.

done.

Olli
Thomas Mahler | 2 Sep 2003 09:29
Picon

Re: Mapping Tutorial Take 1

hi again,

Brian McCallister wrote:
>> 1. with the latest cvs head the jdbc-type attribute is now optional. 
>> If no type is specified, OJB tries to deduce a proper type from the 
>> Java type of the persistent field.
>>
> 
> Excellent, I had thought it should be able to do this. It will be in for 
> 1.0 I presume?

yes.

> 
>> 2. I'd prefer to see some more detail on the overall structure of the 
>> repository.xml and the include mechanism. (As I did it in the 
>> tutorial1.html). But maybe you approach is better as it liberates the 
>> user from too much knowledge about internal things?
>>
> 
> I agree completely that the repository.xml needs a thorough explanation 
> - I also think that the explanation should be orthogonal to using the 
> various API's however.

+1 (there are only very few API dependend things with the repository. 
Setting a isolation level only makes sense for ODMG, auto-update and 
auto-delete have different semantics for ODMG and PB)

>> 3. In the advanced topics section we should also mention mapping of 
>> inheritance hierarchies and polymorphism and link to tutorial3.
(Continue reading)

Brian McCallister | 2 Sep 2003 15:18
Favicon

Re: new committers


On Monday, September 1, 2003, at 07:18 AM, oliver.matz <at> ppi.de wrote:

> Hello,
>
>> -----Original Message-----
>
>> Olli and Brian please sign this agreement and fax it back to
>> the apache
>> office.
>
> done.
>
> Olli
>
>

done as well.

Do they need an ssh public-key?

-Brian
David Mann | 2 Sep 2003 20:44

Mapping multiple objects to the same table

It seems like OJB may have some objection to mapping more than one class to
a table.  Examples of this could be classes with a subset of properties
commonly used in queries (lightweight), .... to allow use of the
PersistenceBroker getCollectionByQuery API.  While it can be subverted by
changing case of the table attribute in the class descriptor, I cannot
determine why the objection in the first place.

Is there any problems in pursuing this pattern of usage ?

David Mann
Montreal

****************************************************************************

This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations. Any distribution, use or copying
of this e-mail or the information it contains by other than an intended
recipient is unauthorized. If you received this e-mail in error, please
advise me (by return e-mail or otherwise) immediately. 

Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux
droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou
copie de ce message ou des renseignements qu'il contient par une personne
autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez
ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de
courriel ou par un autre moyen.
Frédéric Trifiro | 2 Sep 2003 15:29

OQLQuery and collection

Hi everyone,

I have a collection c which contains ids i have to retrieve from the 
database... How can i do such a query ?

I suppose i should use the key word "in" but...

select obj from myclass where id in ... ??

Thank you for any help, Frederic
Thomas Mahler | 3 Sep 2003 09:53
Picon

Re: new committers


> 
> Do they need an ssh public-key?
> 

I don't think so. I can connect to the apache ssh servers without having 
an official public key.

Thomas

> -Brian
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe <at> db.apache.org
> For additional commands, e-mail: ojb-dev-help <at> db.apache.org
> 
> 
Thomas Mahler | 3 Sep 2003 10:03
Picon

Re: Mapping multiple objects to the same table

Hi David,

David Mann wrote:
> It seems like OJB may have some objection to mapping more than one class to
> a table.  

Why do you think so?

> Examples of this could be classes with a subset of properties
> commonly used in queries (lightweight), .... to allow use of the
> PersistenceBroker getCollectionByQuery API.  

Exactly. And that's why we even recommend this kind of mapping as best 
practise for certain situations.

Here is a recent sample posting from our user list:
"I have got a solution of Tomas Mahler and thought that I would share 
it. It is very simple once you realise that there arn't a 1-1 relation 
between class-description and database-table but a n-1. You can have as 
many classes mapping to one database-table as you like and find use of.

So the solution to how to avoid an OutOfMemory error handling blobs are 
to separate your class holding the blob into two. If you like me have a
Picture-class separate them into  PictureInfo and  PictureData where the
PictureInfo holds all values about the picture that are not the 
picture-data while the PictureData only holds the id and data. When you 
need the data of the picture let the PictureInfo-class load an object of 
PictureData (lazy-loading)."

> While it can be subverted by
(Continue reading)


Gmane