Wrong stored procedure name generated when using different DB schemes

Jiri Brazda — Tue, 15 Jul 2008 10:25:41 GMT

Hi,

In this post I have described problems with DDT and different db schemes. It was solved by fix.

Now I have found additional problem - when I force using stored procedure for update, it causes app crash reporting that "Book_Update" stored procedure doesn't exist. This is true since the Book table is in M02 scheme and stored procedures created by DDT are created in the same scheme.

I have solved this issue by manually setting the UpdateStoredProcedureName property on BO to "M02.Book_Update". However it would by nice when the Business Object Mapper generate it automatically.

Thanks

Jiri Brazda

RE: Wrong stored procedure name generated when using different DB schemes

Trent L. Taylor — Tue, 15 Jul 2008 10:25:41 GMT

Thanks, I will look into this on the schema name.

StrataFrame Forum » StrataFrame Application Framework - V1 » Issues » Wrong stored procedure name generated when using different DB schemes

Wrong stored procedure name generated when using different DB schemes

RE: Wrong stored procedure name generated when using different DB schemes