in reply to Eliminating Dynamic SQL Generation with Decision Matrices for Tighter Large Scale Applications

It's interesting that you bring this up. Over the past few weeks, I have been working on a web form that will allow my users to select some parms from a webpage and genereate a set of graphs based on their selections.

Aside from needing to create some indexes to speead the inital load of the page and selection boxes, I previously, hadn't had any concerns about coding in the manner I have. Now, I am concerned that I should rethink my position.

Just to give some background. I have some input in the initial db design, but it needs to be setup in a manner where there is really no maintenance by the users. Once I turn it over to them, it's theirs. I never ever see it again. It will be fed by a .csv file once per month.

How would some of you propose I alter this code?

The resultant webpage is here.

As a side note...I am currently devloping it using MySQL, but the backend db will become MS Access.

perl -e 'print reverse qw/o b n a e s/;'
  • Comment on Re: Eliminating Dynamic SQL Generation with Decision Matrices for Tighter Large Scale Applications