Re: taking orders

>>>>>
Just a note here:  Just because a cart is database driven does NOT mean
that it is going to be slow.  I have designed several sites that contain
over 15,000 items and the search time for an item (or link to an item)
is almost instant.  It simply depends on whether or not you have the
right application for the job.  If a database site is designed
correctly, then it will be just as fast as ANY site could be.
<<<<<

Much agreement!!! What I have discovered is that if you step up to using
an SQL type database, you HAVE TO LEARN SQL, and you HAVE TO LEARN how
to optimize and normalize the database. I don't know how many times I
have seen people complaining about the slowness of a catalog program,
only to have it discovered that they were running a catalog with no
primary keys, not indexes, no optimizations, no normalization of the
database. 

On another note, I have seen some pretty amazing catalogs working with
simple gdbm files (a unix db type of file) that are very fast. I have
also seen catalogs using gdbm files that are as slow as molassas.


-- 


Jim Tom Polk -:- jtpolk(at)texas.net -:- http://camalott.com/~jtpolk/	
	''You might as well fall flat on your face as 
	  lean over too far backwards.''      --James Thurber--
   "The Universe is run by the complex interweaving of three 
          elements: energy, matter and enlightened self-interest." 
 		- G'Kar  "Survivors"                                  

HTML: hwg-basics mailing list archives, maintained by Webmasters @ IWA