[DUG] D2005/Architect
Richard Vowles
Richard.Vowles at borland.com
Tue Jun 21 14:29:28 NZST 2005
> Does ECO support existing database schemas?
Yes
> Does ECO support poorly designed existing database schemas?
Yes
> Does ECO support multiple databases at once?
Yes, but it doesn't do distributed two phase commit on them. Just yet.
> Does ECO support multiple database manufacturers at once?
Yes
> How many different database manufacturers does ECO support?
Out of the box mappers exist for all the Delphi environment supported
ones - IB, Firebird, Oracle, DB2, SQL Server, MySql and
"generic-sql-92". If you want to support another one, then the mappers
are pretty straight forward to write. Further more, you can even write
mappers specifically for certain types of fields and if you wish, you
can decide that writes back to a database are different from reads (one
person suggested writing an xml packet to an MSMQ queue for example to
update the database).
> How far does this support go?
What does that mean?
> How flexible is it?
What does this mean? Can you bypass it and go straight to the db? Can
you write your own persistence services and mappers and so forth? Sure
you can. It is designed to be extremely flexible.
> How hard is it to use? I mean, is the answer yes, but only if you
stand on one foot while
> reciting the national anthem and hopping widdershins around a 100 year
old oak tree?
Like anything that is designed to significantly increase your
productivity, there is a learning curve. How long did it take you to
learn Delphi? Those controls that you purchased? There is always a dip
in productivity to start with as you get used to something. But some ORM
vendors for .NET are claiming 75% productivity boosts - and that is JUST
for ORM. And ECO is _much more_ than ORM.
> How hard is ECO to use in general, when you are using it the "right"
> way?
Its easy. Once you know what you are doing, its really, really easy. And
you will wonder why on earth you did it any other way.
Richard
---
Richard Vowles
Borland Solutions Architect
DDI: +64-9-9184573, Cell: +64-21-467747
email and IM/MSN: richard.vowles at borland.com
Skype: rvowles
-----Original Message-----
From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz]
On Behalf Of Allan, Samuel
Sent: Tuesday, 21 June 2005 2:21 p.m.
To: NZ Borland Developers Group - Delphi List
Subject: RE: [DUG] D2005/Architect
Does ECO support existing database schemas?
Does ECO support poorly designed existing database schemas?
Does ECO support multiple databases at once?
Does ECO support multiple database manufacturers at once?
How many different database manufacturers does ECO support?
How far does this support go?
How flexible is it?
How hard is it to use? I mean, is the answer yes, but only if you stand
on one foot while reciting the national anthem and hopping widdershins
around a 100 year old oak tree?
How hard is ECO to use in general, when you are using it the "right"
way?
More information about the Delphi
mailing list