in reply to Re^2: MySQL Table Creation using DBI
in thread MySQL Table Creation using DBI

I was not replying to your post.

If the poster is new to working with databases, then the best thing to do is to get comfortable with the most straitforward way of doing things, which is with SQL. Not a good idea to abstract out fundamental tools if you don't know how the fundamental tools work. 

()-()
 \"/
  `
  • Comment on Re: Re: Re: MySQL Table Creation using DBI

Replies are listed 'Best First'.
Re^4: MySQL Table Creation using DBI
by adrianh (Chancellor) on Sep 05, 2002 at 21:36 UTC

    Apologies for the misrepresentation. Misread the message hierarchy. Now fixed.

    You can certainly get in a horrible fix if you don't understand that tools like Class::DBI have limitations (the lack of support for multi-column primary keys being a case in point here).

    I think I could argue with the statement that SQL is the most straightforward way of doing the task - but I understand the sentiment ;-)

[reply]
      <soapbox>
      If right out of the gate you are needing to create dynamic constantly changing scripted tables you need to step back and rethink your problem. You are trying to hard. It is easy to fall into the trap of treating tables as just another hash to manipulate. Your data is not mearly a tool that you use in your application. It is your foundation, and you need to keep your foundation as solid and simple as possible. Even The Sistine Chapel is built on a big boring block of rock.

      As someone who has spent a lot of time digging through other people's spaghetti code, there is nothing more horrible then abstract, dynamically generated SQL. Clear, simple, straitforward SQL is like a beacon in even the darkest of nights. Think long and hard before you try something more.

      </soapbox>

      /me goes back to his cave to lick his wounds from his last contract gig. 

      ()-()
 \"/
  `
[reply]

In Section Seekers of Perl Wisdom