> "OR" == Octavian Rasnita writes:
OR> From: "Uri Guttman"
>>
>> it isn't religious. it is just no one is taught the right way
>> anymore. it used to be always done this way (in the good very old
>> day). with the onslaught of redmond and aol the unwashed masses didn't
>> learn
From: "Uri Guttman"
> MC> Uri: I think the quoting is much a religious issue as everyone has their
> MC> preferred way, but I now know what you meant. :-)
>
> it isn't religious. it is just no one is taught the right way
> anymore. it used to be always done this way (in the good very old
> day)
> "MC" == Mimi Cafe writes:
MC> Earlier I thought of using an eval or BEGIN block to evaluate the
MC> SQL, but then I thought wait a minute, that wouldn't be the
MC> correct way of using them. Now I see that doing as you guys
MC> recommended is the right way forward.
a BEGIN block ma
>> -Original Message-
>> I'm talking for myself here, but the way I usually do this is that I wrap
>> up each SQL query or set of related SQL queries in a subroutine.
>>
>> If the sub's going to be used as a predicate I make sure it returns
>> true/false and pass all of the relevant data
Mimi Cafe asked:
> I need to evaluate a statement in an if, elsif, else block, and the
> statement to evaluate in the elsif is too large as I need to run a SQL
> query and act on the return value.
> What would be a better way to achieve this? Putting the SQL statement
> elsewhere outside the block
> "MC" == Mimi Cafe writes:
MC> I need to evaluate a statement in an if, elsif, else block, and
MC> the statement to evaluate in the elsif is too large as I need to
MC> run a SQL query and act on the return value. What would be a
MC> better way to achieve this? Putting the SQL statem
I need to evaluate a statement in an if, elsif, else block, and the
statement to evaluate in the elsif is too large as I need to run a SQL query
and act on the return value.
What would be a better way to achieve this? Putting the SQL statement
elsewhere outside the block cannot be right, so I am wo
