[AccessD] Data interface The best way

I have been playing with Caché recently and found the database creation a
very interesting and refreshing. Totally OOPS (Still getting my head around
that one.) 

I have just been following the tutorials but tried some data importing the
other night and it seems to run very fast... 370,000 records and the data
searches are basically instantaneous. 

Nothing unusual for a major DB but the interesting thing is that I did not
have to specify a database or table or field. Now the next big hurdle is how
this can be attached to Access. (A friend likened it to towing a battle-ship
with a VW.) 

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil
Salakhetdinov
Sent: Wednesday, October 19, 2005 4:48 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Data interface The best way

Hi Gustav,

Yes, there is no single answer to all needs.
Yes, speed isn't that important sometimes.

As for "an object design down to the lowest level" - this is still
questionable here how it should be done - and it's getting the more
questionable what this design should be the more I'm getting into the modern
methods of OOP&D...

...it looks like the more popular is getting a "good old idea" of OOP
founders (Grady Booch etc.) that objects are not "encapsulated data with
behavior" but behavior first of all and encapsulated data are secondary...

...as far as I see this idea is getting into mainstream R&D...

...and as far as I may guess true OO DBMS of the future (5-10 years from
now?) will be quite different from what we see now on the market (I could be
missing something) - the query result of such OO DBMS database will be
objects with behavior not just data, and object with behavior first of
all...

...this is where LINQ will evolve as far as I may guess (is Caché doing
something like that there days?)...

...how this will be done technically is an open question - will they store
something like .NET assemblies in OO database together with data or...?

...the effective OODBMS of the future will become reality when relatively
cheap mutlicore processors with hundreds(thousands, ...?) of cores will
become everyday and mass market things not "expensive technical miracles"...

...will MS be leading in this area in 10 years from now or not? They have
just lost Ward Cunningham who left them to join Eclipse Foundation
(http://www.microsoft-watch.com/article2/0,1995,1872348,00.asp?kc=MWRSS02129
TX1K0000535)...

Shamil

----- Original Message ----- 
From: "Gustav Brock" <Gustav at cactus.dk>
To: <accessd at databaseadvisors.com>
Sent: Tuesday, October 18, 2005 8:20 PM
Subject: Re: [AccessD] Data interface The best way


Hi Shamil

You are right - there is no single answer to all needs and that counts for
db engines as well.
I have no idea where, say, Caché is faster than other solutions, if any, but
I'm sure in _some_ cases it will be. It is difficult to say as Intersystems
as well as other suppliers are very reluctant to publish comparable
benchmarks which reflect real scenarios.

You can also turn it upside down; in some cases speed is not that important
and for such scenarios it an object design down to the lowest level could be
preferable.

As for sheer speed using code, some years ago I posted to the list a routine
for recursive lookup (self referencing a table) using DAO only - and it ran
at a speed that surprised me.

/gustav

<<< tail trimmed>>>

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com