in reply to Re^2: perl & SQL best practices
in thread perl & SQL best practices

So, you have no bottlenecks, no goals (performance wise), you're rather small, and all you can tell about your future is that you're adding "canned applications, along with my custom coding". Yet you ask from us suggestions that will prevent you from saying "Darn, I shoulda" in the future.

What do you expect to get? I mean, even if I said "don't smoke", it doesn't mean it's going to prevent a "darn, I shoulda" in the future. Some people smoke all their life, and never get cancer, and people get cancer who don't smoke.

Seriously, set goals, and measure your performance. Act if necessary. Magic bullets do not exist.

Replies are listed 'Best First'.
Re^4: perl & SQL best practices
by ksublondie (Friar) on Apr 27, 2012 at 23:01 UTC
    So, you have no bottlenecks, no goals (performance wise), you're rather small, and all you can tell about your future is that you're adding "canned applications, along with my custom coding".

    Yea, you're correct.

    What do you expect to get?

    Your advice. Tell me what you do or would do as a programmer if you had complete control over your db server. Are there any practices you yourself follow? Of course, we all use strict. Do you have similar rules you follow and/or made in regards to sql db interaction? Do/would you develop your sql from your perl or instead put it outside on the db server? And what are your reasons for doing it that way?

[reply]
[d/l]
      Tell me what you do or would do as a programmer if you had complete control over your db server.
      How many times do I need to repeat: IT DEPENDS. Define goals. Measure. Know what the budget is. Work out what needs to be done. There are no magic bullets.
      Of course, we all use strict.
      That's like saying: "what should I do when I need to transport something? Of course we all check our headlights first." If you don't tell me what you need to transport from which pickup point to which destination, at what time, what the budget for it is, what your resources are and when it has to be there, don't expect me to tell you whether you should use a bicycle, a pick-up truck a train, or whether you should hire a specialist company. Magic bullets do not exist.
      Do you have similar rules you follow
      I do have rules I follow (but they aren't as mindless, boring and and a bit more useful than "use strict"), and they are: do not do anything without knowing what's going on, what the goal is, and what the budget is (budget is to be taken in a broad sense. It includes, but is not limited to: money, people, time frame, regulations, knowledge). Aka, don't run around as a headless chicken, going in any direction monks in the peanut gallery are shouting to you.
[reply]

        ... as mindless, boring and and a bit more useful than "use strict" ..
        Not to be picky or anything, but the advice to "use strict" is not mindless, nor is it not useful, so you've got two obvious strikes out of three (and an umpire call on the third).

        The point the OP was making should be obvious: there are indeed areas where a consensus exists on what's the best practice, and he wants to hear about others.

        I do have rules I follow ... and they are: do not do anything without knowing what's going on
        So you mean you never do anything?

[reply]

In Section Seekers of Perl Wisdom