Re: Re: mySQL hits or Storable retrieves?

in reply to Re: mySQL hits or Storable retrieves?
in thread mySQL hits or Storable retrieves?

Maybe I'm confused,(in fact I am confused), but maybe I'm specifically confused...

MySQL has got TEMP tables, which are in memory, SQL accessible, databases. I've used these for small data warehouse style problems in the past. They're very fast. Is this what you mean??

-- Anthony Staines

Comment on Re: Re: mySQL hits or Storable retrieves?

Replies are listed 'Best First'.
Re: Re: Re: mySQL hits or Storable retrieves? by Hero Zzyzzx (Curate) on Oct 03, 2001 at 17:35 UTC
The problem is that each "view" if you will, which is a combination of the users' accesslevel and category they are requesting, filtered down by the domain that the request is coming from, requires me to run multiple queries. My understanding was that mySQL had a memory-caching feature for regular tables, in addition to the RAM-only HEAP tables that your alluding to.These views could also get large down the road. (I'm migrating a Lotus Domino (yuck!) NSF that currently has 2,700 documents int it.) I guess I just thought that it'd be faster and more elegant to run the queries that create the data structures I need periodically, store them to disk with Storable and then retrieve them when I need them, rather then keep two different sets of SQL, one for selecting from a memory-only HEAP table and one for updating to the main database. It's actually far simpler for me to solve this problem using multiple SQL queries, too. I'll post example code soon. It's suprisingly (at least to me) simple! -Any sufficiently advanced technology is indistinguishable from doubletalk.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: mySQL hits or Storable retrieves?
by Hero Zzyzzx (Curate) on Oct 03, 2001 at 17:35 UTC

The problem is that each "view" if you will, which is a combination of the users' accesslevel and category they are requesting, filtered down by the domain that the request is coming from, requires me to run multiple queries. My understanding was that mySQL had a memory-caching feature for regular tables, in addition to the RAM-only HEAP tables that your alluding to.These views could also get large down the road. (I'm migrating a Lotus Domino (yuck!) NSF that currently has 2,700 documents int it.)

I guess I just thought that it'd be faster and more elegant to run the queries that create the data structures I need periodically, store them to disk with Storable and then retrieve them when I need them, rather then keep two different sets of SQL, one for selecting from a memory-only HEAP table and one for updating to the main database. It's actually far simpler for me to solve this problem using multiple SQL queries, too.

I'll post example code soon. It's suprisingly (at least to me) simple!

-Any sufficiently advanced technology is
indistinguishable from doubletalk.

[reply]

In Section Seekers of Perl Wisdom