Re: Re: mySQL hits or Storable retrieves?

Wow. Thanks for the very helpful response. Part of my problem here is I think I've normalized my data too much (if that's possible), it's split across so many tables that writing the SQL properly is getting beyond me.

Basically, I'm at the point where I need to run the entire universe of records through a set of filters, akin to:

What documents are in this category/subcategory?
Is the user public, staff, probono attorney, admin, etc.?
What organization is this user from, and what docs are specifically excluded from this organization at this access level?

So, it would be so much easier if I didn't have all this conditional crap. I'd probably do it with one SQL join, but I can't here, I need more than one statement (at least in my head) and I think caching the results is the only way I'm going to get a useable, fast suite of sites.

-Any sufficiently advanced technology is
indistinguishable from doubletalk.

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

Replies are listed 'Best First'.
Re: Re: Re: mySQL hits or Storable retrieves? by mandog (Curate) on Oct 02, 2001 at 21:43 UTC
Creating a few views might help you to get your head around the queries... A database view is a sort of virtual table. You create it with a SELECT statement and then access it like a regular table. `CREATE VIEW view_red_cross_docs AS SELECT <code here> CREATE VIEW view_pro_bono_docs AS SELECT <code here> SELECT <stuff> FROM <joined views>` [download] email: mandog	[reply] [d/l]
Re: Re: Re: Re: mySQL hits or Storable retrieves? by kwoff (Friar) on Oct 03, 2001 at 03:14 UTC
A nitpick: MySQL doesn't support views yet.	[reply]
Re: Re: Re: mySQL hits or Storable retrieves? by perrin (Chancellor) on Oct 02, 2001 at 19:15 UTC
Object-level security? It sounds like you want SPOPS, or even the app server built on top of it, OpenInteract. It has hooks to add caching as well.	[reply]