Re: How to Execute Multiple SQL Updates Using PHP

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Alice Wei wrote:
Hi, I am inquiring on this list to see if it is possible to create a script that takes multiple update statements without my having to write one "SQL" statement for each of the updates. I have a scenario of which I create a table of some sort with some existing information using Flex, and what I am told by my client is that no matter how many records there are on the screen, the users should be able to update any up to all the entries by simply pushing a button. I use Microsoft SQL, which I think that it does allow multiple update query execution. The problem is that I might have to come up with some method to accept all the "POST" variables the user provides into the script. Could anyone please give me some guidance on what kind of function I might use, or whether or not it is possible I can create a script that accepts as many "POST" variables as the users POST? Thanks a lot for your help. Alice

_________________________________________________________________
Check the weather nationwide with MSN Search: Try it now!
http://search.msn.com/results.aspx?q=weather&FORM=WLMTAG

aaahhhh I've just read that one again..

I used to work with a group of russian programmers, one day a client asked a question and for some functionality such as you just described, to which sasha (the webshop manager) said "sure thing, we'll just do some jiggery pockery and make it work" (in a russian accent). Then dmitry (one of the programmers) started to converse and discuss this with the client, 20 seconds later sasha slapped him, stood up and shouted "DMITRY, never EVER explain to a client what jiggery pockery is".

the point.. you're client wants to be able to click a button and update multiple rows on a form - front end wise that's simple, especially in flex - what happens at the back end doesn't matter, that jiggery pockery is your's to do with as you please, and there is no need to do all the updates in a single transaction when you could just as easily do an sql execute for each row.

just my two pennies, unless you've got a good reason to do it all in one or some decent performance gain by doign so, leave it out and have the front end functionality as per the clients requirements.

regards

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux