I didn't say "complex queries". I said "complex expressions". For example sum(c1 + c2), where c1 and c2 are not on the same table. I know it's not very complex, but it's still impossible to do automatically. It only works if I have the table aliases, which I cannot guess.
-----Message d'origine----- De : Brian McCallister [mailto:[EMAIL PROTECTED] Envoyé : mercredi 22 juin 2005 18:21 À : OJB Developers List Objet : Re: OJB 1.1 On Jun 22, 2005, at 2:50 AM, Cosmin MERLUSCA wrote: > Hello, > > I'm using OJB and I would have a number of questions for you: > > 1. Is this project going on or is it going to be stopped? The > answer to this > is critical for the project. I don't foresee it being closed up -- its alive and kicking as far as I can tell. > 2. If is going to continue, when is OJB 1.1 due to come out? Not sure =) > > 3. Will OJB 1.1 solve the problem of complex expressions? I have > spent quite > a lot of time searching the answer to this question, and I have > seen that > there was some work done on 1.0.3, but this is hardly enough. What > I need is > to be able to create complex expressions and if this problem is not > going to > be solved, I can perform SQL queries directly. I just want to know, > so that > I can make a planning on my work and on the directions on which I > should go. What do you mean by "complex queries"? You can get very sophisticated with the PB query API. I don't foresee radical changes in the ODMG OQL implementation in the near future, but I could be wrong. -Brian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
