fixed in trunk. Please check.
On Apr 6, 4:50 pm, DenesL <[email protected]> wrote:
> On Apr 3, 5:23 pm, Yarko Tymciurak <[email protected]> wrote:
>
> > On Fri, Apr 3, 2009 at 3:59 PM, mdipierro <[email protected]> wrote:
>
> > > I do not see a problem with this but is GO a mssql only keyword?
>
> I don't know.
>
>
>
> > In MSSQL - "GO" runs the accumulated batch of lines (it's like "enter").
>
> > The problem is, I think, that you cannot depend on the order of statement
> > exectution when "GO" executes the SQL statements - so you must "complete"
> > table alterations before you use them, and the only way to be sure of it
> > is.... to break up the execution batches.
>
> According to msdn:
> A batch is a group of one or more Transact-SQL statements sent at the
> same time from an application to SQL Server 2005 for execution. SQL
> Server compiles the statements of a batch into a single executable
> unit, called an execution plan. The statements in the execution plan
> are then executed one at a time.
>
> ...so I don't think the order of execution is an issue.
>
> Denes.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
