This project is read-only.

Problem with blobs

Blobs are supported in your app, there is only one error. In sql procedure is declared parameter of type varbinary but it should be varbinary(max). In case of varbinary only 1st byte is saved. Orig...

Id #9740 | Release: None | Updated: Feb 13, 2013 at 7:35 PM by kloken | Created: Mar 22, 2008 at 1:46 AM by kloken

Insert stored procs - Cannot insert an explicit value into a timestamp column.

Msg 273, Level 16, State 1, Procedure sp_Countries_Insert, Line 13 Cannot insert an explicit value into a timestamp column. Use INSERT with a column list to exclude the timestamp column, or insert ...

Id #9266 | Release: None | Updated: Feb 13, 2013 at 7:35 PM by ld9474 | Created: Jan 30, 2008 at 12:16 PM by TomLeeson

update stored procs - Cannot update a timestamp column.

Msg 272, Level 16, State 1, Procedure sp_Countries_Update, Line 14 Cannot update a timestamp column.   Create Procedure sp_Countries_Update ( @CountryID int, @CountryName nvarchar(50), @DateCreated...

Id #9265 | Release: None | Updated: Feb 13, 2013 at 7:35 PM by ld9474 | Created: Jan 30, 2008 at 12:15 PM by TomLeeson

inconsistent naming standards for select stored procs

Example: sp_Addresses_Select_All sp_Addresses_Select_One   foreignKey: sp_Select_Addressess_By_CountryID   should be sp_Addressess_Select_By_CountryID   notice the addressess should be addresses

Id #9264 | Release: None | Updated: Feb 13, 2013 at 7:35 PM by ld9474 | Created: Jan 30, 2008 at 12:10 PM by TomLeeson

Select @@identity used in inserts

Its better to use SELECT scope_identity()

Id #9263 | Release: None | Updated: Feb 13, 2013 at 7:35 PM by ld9474 | Created: Jan 30, 2008 at 12:07 PM by TomLeeson

Cannot specify a column width on data type timestamp.

Timestamps declared as: @DateModified timestamp(8)   Msg 2716, Level 16, State 1, Procedure sp_Addresses_Update, Line 3 Column, parameter, or variable #29: Cannot specify a column width on data typ...

Id #9262 | Release: None | Updated: Feb 13, 2013 at 7:35 PM by ld9474 | Created: Jan 30, 2008 at 12:04 PM by TomLeeson

Smallint - Bigint Columns generate an SQL Error

Just like tinyint, the length of bigint and smallint parameters are written while it should not.

Id #9240 | Release: Iris Generator 1.0.2 | Updated: Jun 12, 2013 at 1:38 AM by ld9474 | Created: Jan 23, 2008 at 8:38 PM by ld9474

CRUD - Adding of plurals in stored procs... adding S where not needed

sp_Select_CompanyCategoriess_By_CategoryID should be sp_Select_CompanyCategories_By_CategoryID

Id #9238 | Release: Iris Generator 1.0.2 | Updated: Jun 12, 2013 at 1:38 AM by ld9474 | Created: Jan 23, 2008 at 1:06 PM by TomLeeson

SP_ Naming is bad practice

The CRUD generator prefixes stored with sp_ This documented bad practice for SQL Server.

Id #9237 | Release: Iris Generator 1.0.2 | Updated: Jun 12, 2013 at 1:38 AM by ld9474 | Created: Jan 23, 2008 at 1:04 PM by TomLeeson

tinyint crud error - SQL incorrect

Msg 2716, Level 16, State 1, Procedure up_Addresses_Insert, Line 3 Column, parameter, or variable #10: Cannot specify a column width on data type tinyint.   Look for the syntax error for tinyint d...

Id #9236 | Release: Iris Generator 1.0.2 | Updated: Jun 12, 2013 at 1:38 AM by ld9474 | Created: Jan 23, 2008 at 12:55 PM by TomLeeson