caching the sql queries

[JZ]

Is there any equivalent of caching sql queries for Python like ADOdb
for PHP? (For those who did not hear about ADODb and its feature :
http://phplens.com/adodb/caching.of.recordsets.html)

 

[JZ]

The Only way is using Com

What do you mean?

 

[=?ISO-8859-1?Q?Gerhard_H=E4ring?=]

On Mon, 15 Sep 2003 12:55:15 +0200, "Luca Calderano"


What do you mean?

Luca was mistaking the ADODB from Microsoft's ActiveX Data Objects (ADO)
with the PHP API of the same name.

-- Gerhard

 

[=?ISO-8859-1?Q?Gerhard_H=E4ring?=]

Is there any equivalent of caching sql queries for Python like ADOdb
for PHP? (For those who did not hear about ADODb and its feature :
http://phplens.com/adodb/caching.of.recordsets.html)

I'm not aware of any such thing for Python, and I find it dubious, too.

In my opinion, this sort of caching should really be done in the
application layer, not in the database access layer.

-- Gerhard

 

[Syver Enstad]

In my opinion, this sort of caching should really be done in the
application layer, not in the database access layer.

I didn't know that PHP programmers used layers at all

On a more serious note, Why do you think caching should be
implemented in the application layer (is this the same as the
domain/business layer) rather than the database access layer?

 

[=?ISO-8859-1?Q?Gerhard_H=E4ring?=]

I didn't know that PHP programmers used layers at all

On a more serious note, Why do you think caching should be
implemented in the application layer (is this the same as the
domain/business layer) rather than the database access layer?

Yes, a dozen different terms for the same thing

It's mostly gut feeling about what's the right approach, which has
served me well quite often

If I needed to state reasons, I'd say that the business layer can assure
data consistency, while with this simplistic approach, the database
layer (*) cannot.

-- Gerhard

(*) "database access layer" may sound like something important, but in
my projects, it's only a thin layer on top of DB-API/ADO.NET/... that
provides shortcuts for the most common use cases and allows switching
database backends more easily.

 

[JZ]

In my opinion, this sort of caching should really be done in the
application layer, not in the database access layer.

Why not? It caches only db recordsets an it is total independend from
other form or cache.