In article <[EMAIL PROTECTED]>,
Stuart Felenstein <[EMAIL PROTECTED]> writes:
> How am I keeping transactions open ? Since I don't
> want to do a transaction till the very end. All I'm
> doing is bringing the data to last stage. After it's
> all been collected.
You don't "keep transactions ope
See interspersed:
--- Joe Audette <[EMAIL PROTECTED]> wrote:
> If you are saying the user would navigate through
> multiple pages updating a table on each page and you
> want to treat all the updates collectively as one
> transaction, that is a bad idea.
I agree, that is what I am trying to not
If you are saying the user would navigate through multiple pages updating a table on
each page and you want to treat all the updates collectively as one transaction, that
is a bad idea. You want to pass all the data required for a single transaction in one
request so it can be committed or rolle
This maybe somewhat of a silly question.
Scenario - I am pretty much a noob at both relational
databases and web programming. I've built most of my
pages using a RAD tool that, for the most part, does a
decent job , if you keep it fairly simple.
One of the limitations is inserts & updates are d
