search

ssteenkiste / nettiers

Automatically exported from code.google.com/p/nettiers
1 stars 0 forks source link

Stored procedures can cause a not in the expected format error. #349

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Stored procedures that have a space (CR\LF) before the "AS" keyword cause an 
invalid format error when creating the Procedures.xml file.

What steps will reproduce the problem?
1. Script a stored procedure with a CR\LF above the "AS" keyword
2. Enter a value in the CustomProcedureStartsWith property that will cause the 
above stored procedure to be included in the ORM code generation.
3. Click play and watch for the *File Created: Procedures.xml in the output 
window. The error should occur.

What is the expected output? 
Custom stored procedure(s) should be generated within the ORM.

What do you see instead?
Template Error message box. Custom sp [Stored procedure name] is not in the 
expected format.

What version of .netTiers and CodeSmith are you using?
.netTiers: 2.3-r852 
CodeSmith: 5.2.2-r11561

Additional information.
This bug seems to occur for stored procedures with or without parameters.
The bug occurred when run against a SQL 2008 db.

Original issue reported on code.google.com by xk...@yahoo.com on 14 Oct 2010 at 2:45

GoogleCodeExporter commented 9 years ago

Original comment by bniemyjski on 15 Oct 2010 at 1:30

GoogleCodeExporter commented 9 years ago 
My change is to StoredProceduresXml.cst, line 887

Svn patch attached.

Original comment by xk...@yahoo.com on 19 Oct 2010 at 8:40

Attachments:

GoogleCodeExporter commented 9 years ago 
Updated patch. Improved Regex query.

Original comment by xk...@yahoo.com on 28 Oct 2010 at 9:20

Attachments:

GoogleCodeExporter commented 9 years ago 
Hello,

This has been fixed in revision 853.

Thanks
-Blake Niemyjski

Original comment by bniemyjski on 29 Oct 2010 at 9:17

GoogleCodeExporter commented 9 years ago

Original comment by bniemyjski on 7 Jan 2011 at 2:44