Re: compiling

• To: Christophe Vigny <cvigny@artprice.com>, ozone-users@ozone-db.org
• Subject: Re: compiling
• From: Falko Braeutigam <falko@smb-tec.com>
• Date: Thu, 16 Nov 2000 10:51:40 +0100
• Delivered-To: softw7-ozone-db:org-ozone-users@ozone-db.org
• In-Reply-To: <3A127A18.536F45E4@artprice.com>
• Organization: SMB
• References: <3A126CA0.2EA818C4@artprice.com> <00111512500605.00465@sheepy> <3A127A18.536F45E4@artprice.com>

On Wed, 15 Nov 2000, Christophe Vigny wrote:
> >%_Using the ozone ant I've got the joined message.
> 
> Does anyone have compil the 0.6 version ?
> 
> The structure is'nt so flat, because there is a lot of other table, it is actualy
> on an rdbms system.
> The advantage are only programming facility.
> 
> no object mapping.
Okay, I see. Basically, the more object mapping is done in your application, the
more it has a OO design and the more benefit you will get out of the use of
ozone.

Because you mentioned just one big table, it seemed to me that your
application is a typical RDBMS app - just a frontend to put together the
parameter of the SQL queries. It's very difficult to port such applications
to ozone. And it's even harder to get a good performance. If such app runs
fine, then I wouldn't change anything. If you have to change something (to
complex code, bad JDBC driver, whatever), then the app needs a major redesign.


Falko
-- 
______________________________________________________________________
Falko Braeutigam                              mailto:falko@smb-tec.com
SMB GmbH                                        http://www.smb-tec.com

• References:
  • Re: compiling
    • From: Falko Braeutigam <falko@smb-tec.com>
  • Re: compiling
    • From: Christophe Vigny <cvigny@artprice.com>

• Prev by Date: Re: compiling
• Next by Date: Re: delete?
• Prev by thread: Re: compiling
• Next by thread: delete?
• Index(es):
  • Date
  • Thread