On 2013-01-11 19:05, Francisco Obispo wrote:
You really don't want this in DBIx::Class, you want fine grain control of
when to fetch from the database, etc. Anyone can build their layer on top of
DBIx::Class to implement caching.
Using something like memcached would save you some database
On 2013-01-10 16:15, Jesse Sheidlower wrote:
In one of my apps, I have a number of tables that contain values that
change very rarely. Think of something like a category table in an
e-commerce app--they're mostly static, but every now and then you need
to change or add or delete a category.
You really don't want this in DBIx::Class, you want fine grain control of when
to fetch from the database, etc. Anyone can build their layer on top of
DBIx::Class to implement caching.
Using something like memcached would save you some database hits, you can
either set the values to expire at
In one of my apps, I have a number of tables that contain values that
change very rarely. Think of something like a category table in an
e-commerce app--they're mostly static, but every now and then you need
to change or add or delete a category. These occasional changes do,
however, need to be
On Thu, Jan 10, 2013 at 10:15 AM, Jesse Sheidlower jes...@panix.com wrote:
Since I don't know when they might
change, I don't know how I could cache them, because when a change is
made it needs to take effect immediately.
These tables are used on almost every request.
Use a cache that
-Message d'origine-
De : Jesse Sheidlower [mailto:jes...@panix.com]
Envoyé : jeudi, 10. janvier 2013 16:16
À : catalyst@lists.scsys.co.uk
Objet : [Catalyst] DB values that change very rarely
In one of my apps, I have a number of tables that contain values that
change very rarely
