Definitely the operations people are probably not it... Depends on the
organization of course... This stems from problems early in the days of
OODBMS when they weren't nearly as robust as an RDBMS, I can't comment if
they'd made much progress. And as Tinou also said, tool integration can be
an issue in terms of report writers, query tools, etc.
Cheers
Jay
-----Original Message-----
From: Tinou Bao [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 02, 2001 3:32 PM
To: [EMAIL PROTECTED]
Subject: Re: Offtopic: Experiences with ODBMS...
comments from a guy who hasn't used one but would like to:
>From what I've read people who use object dbs love it (maybe the ones who
don't like it aren't saying anything...) but the the major things I would
say have prevented us from using versant or the likes are:
* clients don't want anything but oracle/sql server bc they already got it
and it's hard to "go wrong with it"
* integration with 3rd party tools that talk to oracle et al only...versant
et al have java apis and probably adapters for jdbc/sql but it's probably
not officially supported by the product u need to integrate with...
--
Tinou Bao
www.tinou.com
----- Original Message -----
From: "Winston Gnananayagam" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 02, 2001 2:45 PM
Subject: [EJB-INT] Offtopic: Experiences with ODBMS...
> Hi all,
> Can anybody share their experiences in deploying a design
solution
> that involves an ODBMS. Are there any major pitfalls in using a ODBMS to
> persist your objects as opposed to using a relational database. I'm not
> trying to completely avoid a relational database, but I need a odbms that
> could co-exist with a rdbms and take care of persisting my objects.
> I'm right now evaluating some ODBMS products, which will
provide
> simple means for storage and fast retrieval of my objects in a
distributed,
> multi-user environment. Support for retrieving data using complex queries
is
> an absolute necessity.
> My goal is to avoid all the middleware components(O-R Tools)
> that's needed to keep my objects persistent. Hopefully, I'd also avoid
> further bloat of my application without any use of Entity Beans. I'm sure
my
> application would end up with 40% less code. I've been also hearing that
in
> certain cases the applications using odbms products are 10 times faster
than
> the ones using rdbms. Seems like the cost benefits of using an ODBMS
product
> is extremely good as they are a lot cheaper than the existing RDBMS
> products.
> Anyway, my bottom line is, I'm looking for a solution to persist
> my objects and retrieve them fast. I don't need anything fancy at all that
> today's RDBMS products provide. Any pointers/tips/warnings from architects
&
> developers will help me out a lot.
> Winston.
>
>
===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
