equivalent to "GO" stored procedure  
Author Message
RWise





PostPosted: Thu Jan 15 15:47:24 CST 2004 Top

SQL Server >> equivalent to "GO" stored procedure

Hello,

I am using the "go" statement in the Query Analyzer with the following.

ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255) NOT NULL
ALTER TABLE tblWinLossMartAgr ALTER COLUMN Region VARCHAR(255) NOT NULL
ALTER TABLE tblWinLossMartAgr ALTER COLUMN CustomerName VARCHAR(255) NOT
NULL
GO
ALTER TABLE tblWinLossMartAgr ADD CONSTRAINT pk_WinLossMartAgr PRIMARY KEY
CLUSTERED (FiscalQtr, Region, CustomerName)

I need to move this to a stored procedure. Is there an equivalent to the
"go" statement?

--
Thanks in advance,

Steven

SQL Server283  
 
 
Steve





PostPosted: Thu Jan 15 15:47:24 CST 2004 Top

SQL Server >> equivalent to "GO" stored procedure You can execute the ALTER TABLE statements dynamically:

exec('ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255)
NOT NULL')
...
and there will be no need for GO.

I can't help wondering why you would need to do this kind of thing more
than once, though. If this sequence of statements works in Query
Analyzer, then there can't be any data in the table, so can you just
create the table with all the required columns and constraints in place
without needing ALTER TABLE?

SK



>Hello,
>
>I am using the "go" statement in the Query Analyzer with the following.
>
>ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255) NOT NULL
>ALTER TABLE tblWinLossMartAgr ALTER COLUMN Region VARCHAR(255) NOT NULL
>ALTER TABLE tblWinLossMartAgr ALTER COLUMN CustomerName VARCHAR(255) NOT
>NULL
>GO
>ALTER TABLE tblWinLossMartAgr ADD CONSTRAINT pk_WinLossMartAgr PRIMARY KEY
>CLUSTERED (FiscalQtr, Region, CustomerName)
>
> I need to move this to a stored procedure. Is there an equivalent to the
>"go" statement?
>
>
>

 
 
Tom





PostPosted: Thu Jan 15 15:50:32 CST 2004 Top

SQL Server >> equivalent to "GO" stored procedure This is a multi-part message in MIME format.

------=_NextPart_000_0515_01C3DB87.B04537A0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Why are you putting this into a stored proc? It can only be run once during
the lifetime of your table.

--
Tom

---------------------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql




Hello,

I am using the "go" statement in the Query Analyzer with the following.

ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255) NOT NULL
ALTER TABLE tblWinLossMartAgr ALTER COLUMN Region VARCHAR(255) NOT NULL
ALTER TABLE tblWinLossMartAgr ALTER COLUMN CustomerName VARCHAR(255) NOT
NULL
GO
ALTER TABLE tblWinLossMartAgr ADD CONSTRAINT pk_WinLossMartAgr PRIMARY KEY
CLUSTERED (FiscalQtr, Region, CustomerName)

I need to move this to a stored procedure. Is there an equivalent to the
"go" statement?

--
Thanks in advance,

Steven


------=_NextPart_000_0515_01C3DB87.B04537A0
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#d4d0c8>
<DIV><FONT face=3DTahoma size=3D2>Why are you putting this into a stored =
proc?&nbsp;=20
It can only be run once during the lifetime of your table.</FONT></DIV>
<DIV><BR>-- <BR>Tom</DIV>
<DIV>&nbsp;</DIV>
<DIV>---------------------------------------------------------------<BR>T=
homas=20
A. Moreau, BSc, PhD, MCSE, MCDBA<BR>SQL Server MVP<BR>Columnist, SQL =
Server=20
Professional<BR>Toronto, ON Canada<BR><A=20
href=3D"http://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=
/sql</A></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>"Steven K" &lt;<A =



@TK2MSFTNGP10.phx.gbl</A>...</DIV>Hello,<BR><BR>I=20
am using the "go" statement in the Query Analyzer with the=20
following.<BR><BR>ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr=20
VARCHAR(255) NOT NULL<BR>ALTER TABLE tblWinLossMartAgr ALTER COLUMN =
Region=20
VARCHAR(255) NOT NULL<BR>ALTER TABLE tblWinLossMartAgr ALTER COLUMN =
CustomerName=20
VARCHAR(255) NOT<BR>NULL<BR>GO<BR>ALTER TABLE tblWinLossMartAgr ADD =
CONSTRAINT=20
pk_WinLossMartAgr PRIMARY KEY<BR>CLUSTERED (FiscalQtr, Region,=20
CustomerName)<BR><BR>&nbsp; I need to move this to a stored procedure. =
Is there=20
an equivalent to the<BR>"go" statement?<BR><BR>-- <BR>Thanks in=20
advance,<BR><BR>Steven<BR><BR></BODY></HTML>

------=_NextPart_000_0515_01C3DB87.B04537A0--

 
 
Kevin





PostPosted: Thu Jan 15 15:51:23 CST 2004 Top

SQL Server >> equivalent to "GO" stored procedure Just take out the "GO" and put it in the Stored Proc. SPs can hadle this
without "GO". Is this a perm table or temp in nature? You usually do not
add DDL for perm tables into procs.



> Hello,
>
> I am using the "go" statement in the Query Analyzer with the following.
>
> ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255) NOT NULL
> ALTER TABLE tblWinLossMartAgr ALTER COLUMN Region VARCHAR(255) NOT NULL
> ALTER TABLE tblWinLossMartAgr ALTER COLUMN CustomerName VARCHAR(255) NOT
> NULL
> GO
> ALTER TABLE tblWinLossMartAgr ADD CONSTRAINT pk_WinLossMartAgr PRIMARY KEY
> CLUSTERED (FiscalQtr, Region, CustomerName)
>
> I need to move this to a stored procedure. Is there an equivalent to the
> "go" statement?
>
> --
> Thanks in advance,
>
> Steven
>
>


 
 
Kevin





PostPosted: Thu Jan 15 15:54:17 CST 2004 Top

SQL Server >> equivalent to "GO" stored procedure You do not need to do this dynamically, you can can use it in straight SQL
code in the proc.



> You can execute the ALTER TABLE statements dynamically:
>
> exec('ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255)
> NOT NULL')
> ...
> and there will be no need for GO.
>
> I can't help wondering why you would need to do this kind of thing more
> than once, though. If this sequence of statements works in Query
> Analyzer, then there can't be any data in the table, so can you just
> create the table with all the required columns and constraints in place
> without needing ALTER TABLE?
>
> SK
>

>
> >Hello,
> >
> >I am using the "go" statement in the Query Analyzer with the following.
> >
> >ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255) NOT
NULL
> >ALTER TABLE tblWinLossMartAgr ALTER COLUMN Region VARCHAR(255) NOT NULL
> >ALTER TABLE tblWinLossMartAgr ALTER COLUMN CustomerName VARCHAR(255) NOT
> >NULL
> >GO
> >ALTER TABLE tblWinLossMartAgr ADD CONSTRAINT pk_WinLossMartAgr PRIMARY
KEY
> >CLUSTERED (FiscalQtr, Region, CustomerName)
> >
> > I need to move this to a stored procedure. Is there an equivalent to
the
> >"go" statement?
> >
> >
> >
>


 
 
Steve





PostPosted: Fri Jan 16 11:36:46 CST 2004 Top

SQL Server >> equivalent to "GO" stored procedure Kevin,

The parser will raise an error because it doesn't parse the final
statement based on the altered table. You'll get an error because it
thinks you are trying to create a primary key on a nullable column:

Server: Msg 8111, Level 16, State 1, Procedure p, Line 5
Cannot define PRIMARY KEY constraint on nullable column in table
'tblWinLossMartAgr'.
Server: Msg 1750, Level 16, State 1, Procedure p, Line 5
Could not create constraint. See previous errors.

SK



>You do not need to do this dynamically, you can can use it in straight SQL
>code in the proc.
>


>
>
>>You can execute the ALTER TABLE statements dynamically:
>>
>>exec('ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255)
>>NOT NULL')
>>...
>>and there will be no need for GO.
>>
>>I can't help wondering why you would need to do this kind of thing more
>>than once, though. If this sequence of statements works in Query
>>Analyzer, then there can't be any data in the table, so can you just
>>create the table with all the required columns and constraints in place
>>without needing ALTER TABLE?
>>
>>SK
>>

>>
>>
>>
>>>Hello,
>>>
>>>I am using the "go" statement in the Query Analyzer with the following.
>>>
>>>ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255) NOT
>>>
>>>
>NULL
>
>
>>>ALTER TABLE tblWinLossMartAgr ALTER COLUMN Region VARCHAR(255) NOT NULL
>>>ALTER TABLE tblWinLossMartAgr ALTER COLUMN CustomerName VARCHAR(255) NOT
>>>NULL
>>>GO
>>>ALTER TABLE tblWinLossMartAgr ADD CONSTRAINT pk_WinLossMartAgr PRIMARY
>>>
>>>
>KEY
>
>
>>>CLUSTERED (FiscalQtr, Region, CustomerName)
>>>
>>> I need to move this to a stored procedure. Is there an equivalent to
>>>
>>>
>the
>
>
>>>"go" statement?
>>>
>>>
>>>
>>>
>>>
>
>
>
>

 
 
Kevin





PostPosted: Fri Jan 16 15:33:00 CST 2004 Top

SQL Server >> equivalent to "GO" stored procedure No error for me. We are not dealing with nullable columns, that would be a
different problem. His first problem has "NOT NULL" on all altered columns.
Here is syntax, test it --

USE TEMPDB
GO
IF EXISTS (SELECT 1 FROM TEMPDB..SYSOBJECTS WHERE NAME = 'TBLWINLOSSMARTAGR'
AND XTYPE = 'U')
BEGIN
DROP TABLE TBLWINLOSSMARTAGR
END
IF EXISTS (SELECT 1 FROM TEMPDB..SYSOBJECTS WHERE NAME = 'ADD_COL' AND XTYPE
= 'P')
BEGIN
DROP PROC ADD_COL
END
GO
CREATE TABLE TBLWINLOSSMARTAGR
(
ID INT NOT NULL
, FISCALQTR INT NOT NULL
, REGION INT NOT NULL
, CUSTOMERNAME INT NOT NULL
)
GO
EXEC SP_HELP TBLWINLOSSMARTAGR
GO
CREATE PROC ADD_COL
AS
ALTER TABLE TBLWINLOSSMARTAGR ALTER COLUMN FISCALQTR VARCHAR(255) NOT NULL
ALTER TABLE TBLWINLOSSMARTAGR ALTER COLUMN REGION VARCHAR(255) NOT NULL
ALTER TABLE TBLWINLOSSMARTAGR ALTER COLUMN CUSTOMERNAME VARCHAR(255) NOT
NULL
ALTER TABLE TBLWINLOSSMARTAGR ADD CONSTRAINT PK_WINLOSSMARTAGR PRIMARY KEY
CLUSTERED (FISCALQTR, REGION, CUSTOMERNAME)
GO
EXEC ADD_COL
GO
EXEC SP_HELP TBLWINLOSSMARTAGR




> Kevin,
>
> The parser will raise an error because it doesn't parse the final
> statement based on the altered table. You'll get an error because it
> thinks you are trying to create a primary key on a nullable column:
>
> Server: Msg 8111, Level 16, State 1, Procedure p, Line 5
> Cannot define PRIMARY KEY constraint on nullable column in table
> 'tblWinLossMartAgr'.
> Server: Msg 1750, Level 16, State 1, Procedure p, Line 5
> Could not create constraint. See previous errors.
>
> SK
>

>
> >You do not need to do this dynamically, you can can use it in straight
SQL
> >code in the proc.
> >


> >
> >
> >>You can execute the ALTER TABLE statements dynamically:
> >>
> >>exec('ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255)
> >>NOT NULL')
> >>...
> >>and there will be no need for GO.
> >>
> >>I can't help wondering why you would need to do this kind of thing more
> >>than once, though. If this sequence of statements works in Query
> >>Analyzer, then there can't be any data in the table, so can you just
> >>create the table with all the required columns and constraints in place
> >>without needing ALTER TABLE?
> >>
> >>SK
> >>

> >>
> >>
> >>
> >>>Hello,
> >>>
> >>>I am using the "go" statement in the Query Analyzer with the following.
> >>>
> >>>ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255) NOT
> >>>
> >>>
> >NULL
> >
> >
> >>>ALTER TABLE tblWinLossMartAgr ALTER COLUMN Region VARCHAR(255) NOT NULL
> >>>ALTER TABLE tblWinLossMartAgr ALTER COLUMN CustomerName VARCHAR(255)
NOT
> >>>NULL
> >>>GO
> >>>ALTER TABLE tblWinLossMartAgr ADD CONSTRAINT pk_WinLossMartAgr PRIMARY
> >>>
> >>>
> >KEY
> >
> >
> >>>CLUSTERED (FiscalQtr, Region, CustomerName)
> >>>
> >>> I need to move this to a stored procedure. Is there an equivalent to
> >>>
> >>>
> >the
> >
> >
> >>>"go" statement?
> >>>
> >>>
> >>>
> >>>
> >>>
> >
> >
> >
> >
>


 
 
Steve





PostPosted: Fri Jan 16 16:18:05 CST 2004 Top

SQL Server >> equivalent to "GO" stored procedure Kevin,

If the columns are initially NULL and only changed to NOT NULL by the
ALTER TABLE statements, the error will occur. I assumed what I thought
was a plausible reason to alter columns before adding a primary key on
them, to alter them from nullable to not nullable. If he is changing
the types, but not the nullability, then the error I mentioned will not
occur.

SK



>No error for me. We are not dealing with nullable columns, that would be a
>different problem. His first problem has "NOT NULL" on all altered columns.
>Here is syntax, test it --
>
>USE TEMPDB
>GO
>IF EXISTS (SELECT 1 FROM TEMPDB..SYSOBJECTS WHERE NAME = 'TBLWINLOSSMARTAGR'
>AND XTYPE = 'U')
> BEGIN
> DROP TABLE TBLWINLOSSMARTAGR
> END
>IF EXISTS (SELECT 1 FROM TEMPDB..SYSOBJECTS WHERE NAME = 'ADD_COL' AND XTYPE
>= 'P')
> BEGIN
> DROP PROC ADD_COL
> END
>GO
>CREATE TABLE TBLWINLOSSMARTAGR
>(
> ID INT NOT NULL
>, FISCALQTR INT NOT NULL
>, REGION INT NOT NULL
>, CUSTOMERNAME INT NOT NULL
>)
>GO
>EXEC SP_HELP TBLWINLOSSMARTAGR
>GO
>CREATE PROC ADD_COL
>AS
>ALTER TABLE TBLWINLOSSMARTAGR ALTER COLUMN FISCALQTR VARCHAR(255) NOT NULL
>ALTER TABLE TBLWINLOSSMARTAGR ALTER COLUMN REGION VARCHAR(255) NOT NULL
>ALTER TABLE TBLWINLOSSMARTAGR ALTER COLUMN CUSTOMERNAME VARCHAR(255) NOT
>NULL
>ALTER TABLE TBLWINLOSSMARTAGR ADD CONSTRAINT PK_WINLOSSMARTAGR PRIMARY KEY
>CLUSTERED (FISCALQTR, REGION, CUSTOMERNAME)
>GO
>EXEC ADD_COL
>GO
>EXEC SP_HELP TBLWINLOSSMARTAGR
>
>


>
>
>>Kevin,
>>
>> The parser will raise an error because it doesn't parse the final
>>statement based on the altered table. You'll get an error because it
>>thinks you are trying to create a primary key on a nullable column:
>>
>>Server: Msg 8111, Level 16, State 1, Procedure p, Line 5
>>Cannot define PRIMARY KEY constraint on nullable column in table
>>'tblWinLossMartAgr'.
>>Server: Msg 1750, Level 16, State 1, Procedure p, Line 5
>>Could not create constraint. See previous errors.
>>
>>SK
>>

>>
>>
>>
>>>You do not need to do this dynamically, you can can use it in straight
>>>
>>>
>SQL
>
>
>>>code in the proc.
>>>


>>>
>>>
>>>
>>>
>>>>You can execute the ALTER TABLE statements dynamically:
>>>>
>>>>exec('ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255)
>>>>NOT NULL')
>>>>...
>>>>and there will be no need for GO.
>>>>
>>>>I can't help wondering why you would need to do this kind of thing more
>>>>than once, though. If this sequence of statements works in Query
>>>>Analyzer, then there can't be any data in the table, so can you just
>>>>create the table with all the required columns and constraints in place
>>>>without needing ALTER TABLE?
>>>>
>>>>SK
>>>>

>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Hello,
>>>>>
>>>>>I am using the "go" statement in the Query Analyzer with the following.
>>>>>
>>>>>ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255) NOT
>>>>>
>>>>>
>>>>>
>>>>>
>>>NULL
>>>
>>>
>>>
>>>
>>>>>ALTER TABLE tblWinLossMartAgr ALTER COLUMN Region VARCHAR(255) NOT NULL
>>>>>ALTER TABLE tblWinLossMartAgr ALTER COLUMN CustomerName VARCHAR(255)
>>>>>
>>>>>
>NOT
>
>
>>>>>NULL
>>>>>GO
>>>>>ALTER TABLE tblWinLossMartAgr ADD CONSTRAINT pk_WinLossMartAgr PRIMARY
>>>>>
>>>>>
>>>>>
>>>>>
>>>KEY
>>>
>>>
>>>
>>>
>>>>>CLUSTERED (FiscalQtr, Region, CustomerName)
>>>>>
>>>>>I need to move this to a stored procedure. Is there an equivalent to
>>>>>
>>>>>
>>>>>
>>>>>
>>>the
>>>
>>>
>>>
>>>
>>>>>"go" statement?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>
>
>
>

 
 
Steve





PostPosted: Fri Jan 16 16:21:13 CST 2004 Top

SQL Server >> equivalent to "GO" stored procedure



>No error for me. We are not dealing with nullable columns, that would be a
>different problem. His first problem has "NOT NULL" on all altered columns.
>Here is syntax, test it --
>
>
Just in case my first answer wasn't clear, you might not realize that
ALTER TABLE .. ALTER COLUMN can be used simply to change a column's
nullability:

create table T (
i int null
)
go

alter table T alter column i int not null
go

drop table T

SK

>USE TEMPDB
>GO
>IF EXISTS (SELECT 1 FROM TEMPDB..SYSOBJECTS WHERE NAME = 'TBLWINLOSSMARTAGR'
>AND XTYPE = 'U')
> BEGIN
> DROP TABLE TBLWINLOSSMARTAGR
> END
>IF EXISTS (SELECT 1 FROM TEMPDB..SYSOBJECTS WHERE NAME = 'ADD_COL' AND XTYPE
>= 'P')
> BEGIN
> DROP PROC ADD_COL
> END
>GO
>CREATE TABLE TBLWINLOSSMARTAGR
>(
> ID INT NOT NULL
>, FISCALQTR INT NOT NULL
>, REGION INT NOT NULL
>, CUSTOMERNAME INT NOT NULL
>)
>GO
>EXEC SP_HELP TBLWINLOSSMARTAGR
>GO
>CREATE PROC ADD_COL
>AS
>ALTER TABLE TBLWINLOSSMARTAGR ALTER COLUMN FISCALQTR VARCHAR(255) NOT NULL
>ALTER TABLE TBLWINLOSSMARTAGR ALTER COLUMN REGION VARCHAR(255) NOT NULL
>ALTER TABLE TBLWINLOSSMARTAGR ALTER COLUMN CUSTOMERNAME VARCHAR(255) NOT
>NULL
>ALTER TABLE TBLWINLOSSMARTAGR ADD CONSTRAINT PK_WINLOSSMARTAGR PRIMARY KEY
>CLUSTERED (FISCALQTR, REGION, CUSTOMERNAME)
>GO
>EXEC ADD_COL
>GO
>EXEC SP_HELP TBLWINLOSSMARTAGR
>
>


>
>
>>Kevin,
>>
>> The parser will raise an error because it doesn't parse the final
>>statement based on the altered table. You'll get an error because it
>>thinks you are trying to create a primary key on a nullable column:
>>
>>Server: Msg 8111, Level 16, State 1, Procedure p, Line 5
>>Cannot define PRIMARY KEY constraint on nullable column in table
>>'tblWinLossMartAgr'.
>>Server: Msg 1750, Level 16, State 1, Procedure p, Line 5
>>Could not create constraint. See previous errors.
>>
>>SK
>>

>>
>>
>>
>>>You do not need to do this dynamically, you can can use it in straight
>>>
>>>
>SQL
>
>
>>>code in the proc.
>>>


>>>
>>>
>>>
>>>
>>>>You can execute the ALTER TABLE statements dynamically:
>>>>
>>>>exec('ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255)
>>>>NOT NULL')
>>>>...
>>>>and there will be no need for GO.
>>>>
>>>>I can't help wondering why you would need to do this kind of thing more
>>>>than once, though. If this sequence of statements works in Query
>>>>Analyzer, then there can't be any data in the table, so can you just
>>>>create the table with all the required columns and constraints in place
>>>>without needing ALTER TABLE?
>>>>
>>>>SK
>>>>

>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Hello,
>>>>>
>>>>>I am using the "go" statement in the Query Analyzer with the following.
>>>>>
>>>>>ALTER TABLE tblWinLossMartAgr ALTER COLUMN FiscalQtr VARCHAR(255) NOT
>>>>>
>>>>>
>>>>>
>>>>>
>>>NULL
>>>
>>>
>>>
>>>
>>>>>ALTER TABLE tblWinLossMartAgr ALTER COLUMN Region VARCHAR(255) NOT NULL
>>>>>ALTER TABLE tblWinLossMartAgr ALTER COLUMN CustomerName VARCHAR(255)
>>>>>
>>>>>
>NOT
>
>
>>>>>NULL
>>>>>GO
>>>>>ALTER TABLE tblWinLossMartAgr ADD CONSTRAINT pk_WinLossMartAgr PRIMARY
>>>>>
>>>>>
>>>>>
>>>>>
>>>KEY
>>>
>>>
>>>
>>>
>>>>>CLUSTERED (FiscalQtr, Region, CustomerName)
>>>>>
>>>>>I need to move this to a stored procedure. Is there an equivalent to
>>>>>
>>>>>
>>>>>
>>>>>
>>>the
>>>
>>>
>>>
>>>
>>>>>"go" statement?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>
>
>
>