Custom Stored Procedures are being erased.

I have a problem with Nettiers version 2.0.1.471. It's easy to reproduce.
 1) Create a table with a column named "colX"
 2) Create a Custom Stored Procedure that specify the name of the "colX" in the order by clause (for example)
 3) Generate and everything will be OK
 4) Drop the column of the table
 5) Regenerate again
The problem is that the stored procedure is dropped by the generation process. It disappears. Although the stored is wrong and must be corrected, we run the risk to lose very important code in this stored procedures.
Nettiers in previous versions didn't modify the code of the custom stored.
I hope that this post serves to fix this bug.

I have exactly the same problem. Two times my custom stored procedures had been deleted on same conditions (Nettiers version 2.0.1.471)

Are either of you by chance using the same prefix for your custom stored procedures as the nettiers generated procedures?

-Ryan

I initially used "_{0}_" as custom store's format string, tried later with "sp_{0}_" and problems repeats.

I create a "Clients" table with "IdClient", "Name" and "BirthDate" columns. Then i make a custom store named "sp_Clients_Show":

SELECT *

FROM Clients

ORDER BY BirthDate

Generate templates (NetTiers 2.0.1.471) and it compiles ok. Then i remove "BirthDate" column from "Clients" table and try to regenerate again.

This is the awaited error message that appears on Codesmith generation report.

• StoredProcedures.sql

Error while execution Sql file. System.Data.SqlClient.SqlException: Invalid column name 'BirthDate'.
   en System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   en System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   en System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   en System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   en System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   en System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   en System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   en MoM.Templates.CommonSqlCode.ExecuteSqlInFile(String pathToScriptFile, String connectionString)
   en _CodeSmith.NetTiers_cst.Go()

 With regards to removing a column see if this thread helps... http://community.codesmithtools.com/forums/p/5091/20376.aspx#20376

hth

swin 

This is a known issue and was resolved in SVN version 491.  Please get the latest branch from SVN or download one of the nightly builds after 2/19/07.

http://community.codesmithtools.com/forums/p/5414/21477.aspx#22409

This problem is not related with dropping a column.

swin:

 With regards to removing a column see if this thread helps... http://community.codesmithtools.com/forums/p/5091/20376.aspx#20376

hth

The problem is when you drop a column that is being used by a custom stored procedure and the stored became non-compilable. If you re-generate with the stored procedure in this state, this stored is dropped after re-generation ends