thing.  Which I just don’t get.

If you are a programming, why would you use views?  It is adding a layer of abstraction between the logic and database in an interpreted language with a framework that is already bloated beyond all recognition.  I know when I write plugins for WordPress, I want the plugin to be quick, precise, and add the least amount of overhead possible.  Views just seem to be a way to do all the opposites of those, just for the hell of it.

If you are not very technically inclined, I understand.  Using views is a lot like using MS Access.  You can create fairly complex queries yourself, without having to get someone that actually understands it involved.  And that is the trade off.  You can do it yourself, and eat the extra overhead, or pay/hire/bribe/cajole someone else into doing it for you, specialized, and thus, in theory at least, more efficiently.

These folks claimed to be programmers though, so I just don’t get it.  Why are you depending on someone else’s plugin, that extends functionality that is inefficient and clumsy, can’t do everything, and still requires custom code to be written or even more plugins to be added.  Where exactly does that circular line stop?

The Drupal “framework” and I use that term loosely since it is really a CMS that can just be extended, has enough problems and bloat in it, why exactly are views worth adding more?  Again, assuming you know SQL and PHP on even a basic level.

It just doesnt make any sense.  Query writers and views are one thing if you are working directly with the database, (e.g. phpMyAdmin or TOAD), but adding it as a layer to a “custom” application that you will be supporting when you claim to be capable of actual programming!!??  Please explain that one to me.

To be fair, I dont use Drupal much, I like WP much better.  The OO approach is much more appealing than the very Perl-esque (read: old) way of doing things Drupal does with its modules. But I still don’t get what the big deal is about Views.

Related articles by Zemanta

• Before You Customize Any Part of Your WordPress (wpthoughts.com)
• Choosing an Open Source CMS — Planning, Playing, and Page Views (ostatic.com)
• 7 Suggestions for New Drupal Users in Higher Education (trellon.com)

Now, as someone that has been doing development long enough to know, there are times that code just gets away from the development team and becomes a mess unto itself.  It happens, especially in the OSS world where code reviews are few if ever.  But, as I read the forums for this thing, the developers are just fooling themselves thinking the code is in good shape.

Here are a few basic suggestions:
1) Check to see if the page needs to execute the plugin.  If it doesnt, dont do it.  There is no reason to increase the number of queries by an order of magantuide when I am on a page that has no WP Ecommerce functionality.
2) Clean up the queries.  For example:
SELECT `id` FROM `wp_product_list` WHERE `active` IN(’1′)
should be
SELECT `id` FROM `wp_product_list` WHERE `active` = 1
It is more effiecent.

3) Index the tables!  The query above doesnt use an index.  That is right folks, the field “active” in product_list is not indexed.  This is easy and simple.

4) Use arrays or some other data structure for complex data.  Dont use the same basic query over and over again.  Example: