Wrong stored procedure name generated when using different DB schemes


Author
Message
Trent Taylor
Trent Taylor
StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 6.9K
Thanks, I will look into this on the schema name.
Jiri Brazda
Jiri Brazda
StrataFrame User (146 reputation)StrataFrame User (146 reputation)StrataFrame User (146 reputation)StrataFrame User (146 reputation)StrataFrame User (146 reputation)StrataFrame User (146 reputation)StrataFrame User (146 reputation)StrataFrame User (146 reputation)StrataFrame User (146 reputation)
Group: StrataFrame Users
Posts: 78, Visits: 356
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

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search