Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number

Re: The ONE way of the Web Page

by Masem (Monsignor)
on Nov 01, 2001 at 02:15 UTC ( #122445=note: print w/replies, xml ) Need Help??

in reply to The ONE way of the Web Page

What is the ONE BEST way to query a database table and display it as a web page?
What is the ONE BEST way to identify a user?
What is the ONE BEST way to create a web page?
What is the ONE BEST way to edit a database record?
What is the ONE BEST way to query a database?
And I respond:
There is no best way for any of these.
For every situation, there is a better way than most to accomplish a task. However, what works best in situation A may not work best in situation B.

Differences in hardware (CPU model) is a start , as some software isn't available for all builds as of yet. Then you need to think about the OS and/or distribution vendor, as some tools work better on some CPUs than others. Then you need to worry about versions of those installed tools. What may be a great solution in a 1.0 version may be the worst solution in a 1.1 version due to changes in the tool backends.

Then you have differences in policy that might be set at the upper levels. Maybe you need to develop a solution that works with all other developers, thus limiting tools that might be guru's dreams that are also newbie's nightmares. Maybe you have to use very specific tools that are set by company security or policy, such as a specific version of perl or modules as have been cleared by an IT auditing team. And of course there is the structure of the team that is designing the program; does code separation from display have to be done to allow the graphic artists a stab?

And then there's personal preference. If monk A used tool Y for years, and monk B used tool Z (that does the same thing as Y) for years, there's no way that A and B will concur on the best tool.

In other words, we cannot even begin to recommend the BEST way to do something. We can say which solutions are *stupid* (such as reinventing, and we can offer *numerous* possible solutions, but it's up to the asker to evaluate those solutions and decide which is the best way in the asker's environment to proceed.

Computer programming is another form of engineering. There is no right or wrong answers. A good engineer knows how to think about all the possible solutions and evalute the one that works best.

Dr. Michael K. Neylon - || "You've left the lens cap of your mind on again, Pinky" - The Brain
"I can see my house from here!"
It's not what you know, but knowing how to find it if you don't know that's important

Replies are listed 'Best First'.
Re: Re: The ONE way of the Web Page
by mdupont (Scribe) on Nov 01, 2001 at 14:23 UTC
    Dear Fellow Monks, From your responses is time for me to be alot more humble! I therefor put my foot in my mouth, and admit what I really want to ask is :

    Dear fellow perlmonks,

    I am cosidering putting a couple of queries and table edits on our corporate intranet web page and would like to use apache/perl and DBI DBD::Sybase running on solaris or debian.

    I am confused by all of the competing Modules that offer variying degrees of flexability. I am lost at the multitude of choices.

    Has anyone any experience with any or all of them? can the perlmonks recommend anyone of them?

    The real question is for me, what is the best place to start building a simple query application where I can reuse all of these nice html tools and still have a place to grow into?

    A query builder like MSAccess with a datatable is what I am thinking about, or even a HTML isql window....

    Yours truly,


      Now this is a real question, and it should be in Seekers of Perl Wisdom. However, here is a brief opinion:

      None of the tools you mention here are widely used. That doesn't mean they stink, but it does mean they are either too new or not generally useful enough to have attracted many followers.

      One friend of mine did try DBIx::Abstract, and liked it, but in general I think the most efficient way to build a simple query application is the most obvious: use CGI and DBI. SQL isn't hard, and I generally find it much easier to write it directly than to use any of the abstraction layers I've tried. CGI is dirt simple, and it's easy to add in templating if you want to, with a popular module like Template Toolkit or HTML::Template.

      If these really seem too low-level to you, I would suggest you post your question in Seekers of Perl Wisdom, and phrase it along the lines of "What's a good high-level tool for quickly building simple database editing apps?"

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://122445]
and the sunlight beams...

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (3)
As of 2018-07-19 02:19 GMT
Find Nodes?
    Voting Booth?
    It has been suggested to rename Perl 6 in order to boost its marketing potential. Which name would you prefer?

    Results (398 votes). Check out past polls.