Re: RDMS Database's and/or Record Managers

new topic     » goto parent     » topic index » view thread      » older message » newer message

Hey Ray,

I think you might have missed what I was after.

RDBMS and / or Record Manager

then I gave what tsunami is "in a nut shell" and welcomed comments. 
I wasnt suggesting this is better than that or whatever (well to an extent).

I appreciate your comments and welcome you to give the tsunami 
wrapper a try if just to take a quick look..

I personally think that those using EDS that need more power should
try tsunami, those who need multi-user support, multiple key search's 
from within each record (if needed), speed, recovery, rebuilds, only
38 commands to learn and full control over any type data, etc...

Thanks Ray,
Euman

----- Original Message ----- 
From: "Ray Smith" <smithr at ix.net.au>
To: <EUforum at topica.com>
Sent: Wednesday, January 21, 2004 11:11 PM
Subject: RE: RDMS Database's and/or Record Managers

> Euman wrote:
> > From: "Ray Smith" <smithr at ix.net.au>
> 
> [snip]
> 
> > > but I dont believe you are giving people the full picture of what RDBMS 
> > > can do.
> > 
> > Why would i? 
> 
> Because you are giving an overview of Databases vs Record Managers 
> and then saying how good record managers are.  
> 
> >Have you even given tsunami a look Ray?
> 
> I looked at the tsunami record manager in the past but not since you 
> created your eu wrappers.
> I'm not saying the tsunami record manager is bad in anyway at all.
> 
> > Just how much easier is this than the tsunami wrappers?
> > 1) to learn
> > 2) for speed
> > 3) for security (any encryption routine will do, there are several in 
> > the RDS archive)
> >                     *(Tsunami Pro has built-in encryption)
> > 4) total control of your data
> 
> I listed (and hence agree) that there is more work in setting up and 
> mainting a RDBMS.
> >From a programming point of view SQL can give you alot of flexibility
> and power that record managers don't give you.  And yes, it will take
> more time for a developer to learn these things but that time should
> be recoped in the long term by the efficiency of these powerful 
> tools and technologies.
> 
> > > The Pros for RDBMS
> > > 
> > > A good RDBMS is "almost" always required for large and complex
> > > projects.
> > 
> > Is this true? 
> 
> I beleive it's true.
> 
> >Can you see anything written useing euphoria's speed for large projects 
> >anyway?
> 
> I agree, I personally don't think Euphoria can handle large complex 
> systems.
> That doesn't mean that I wouldn't use a database for a Euphoria
> project though ;)
> Just like in some cases record managers "could" be used in some large
> complex systems.
> 
> Every case needs to be reviewed and a decision made based on the 
> features required.
> 
> The only reason I replied in the first place was that "I" thought 
> you gave a one sided view.
> 
> Ray Smith
> http://rays-web.com

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu