Update Using Stored Procedure Issue


Author
Message
Trent Taylor
Trent Taylor
StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 6.9K
Great to hear! Smile
Larry Caylor
Larry Caylor
Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)
Group: Awaiting Activation
Posts: 592, Visits: 3.7K
Just installed the latest beta... problem fixedBigGrin Thanks!
Trent Taylor
Trent Taylor
StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)StrataFrame Developer (8.7K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 6.9K
This has now been corrected and will be included in the update I post later in the day.  Thanks for the heads up Smile  A new setting called Primary Key Is Updatable has been added, which by default should just be left alone as the BOs new property PrimaryKeyIsUpdatable defaults to False as well. 


Larry Caylor
Larry Caylor
Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)
Group: Awaiting Activation
Posts: 592, Visits: 3.7K
This is still messed up in 1.65 beta. There is a mismatch between DDT and the Framework where an object has a non-autoincrementing integer PK and the DDT is asked to create Insert & Update sprocs. Attached are screenshots of the sp created by DDT, the exception when the program is run, and the sql debug.

-Larry

Attachments
Exception.png (137 views, 41.00 KB)
UpdateSP.png (136 views, 16.00 KB)
Debug.png (147 views, 27.00 KB)
StrataFrame Team
S
StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)
Group: StrataFrame Developers
Posts: 3K, Visits: 2.5K
OK, I'll change the DDT so that it maches what's in the SqlDataSourceItem within the next release.  Thanks, Larry.
Larry Caylor
Larry Caylor
Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)
Group: Awaiting Activation
Posts: 592, Visits: 3.7K
Looks like my initial test of the fix was flawedBlush It turns out that the updated DDT is appending "_ORG" to the primary key name when it creates the update stored procedure for a non-identiy PK. The framework is appending "_ORGPK" when it creates the SQL command, so of course it fails. For now I've just modified SqlDataSoruceItem to append "_ORG" since I have the source and that is easier than modifying the stored procedures.

-Larry

StrataFrame Team
S
StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)
Group: StrataFrame Developers
Posts: 3K, Visits: 2.5K
Hrm... no idea what that could have been, but yeah, the last few days have been DDT days... several fixes made their way in Wink
Larry Caylor
Larry Caylor
Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)Advanced StrataFrame User (902 reputation)
Group: Awaiting Activation
Posts: 592, Visits: 3.7K
Thanks Ben. That fixed the problem. Looks like there were some other changes too. I was having an issue with role base security that went awaywhen I redeployed the database using the new DDT.

-Larry

StrataFrame Team
S
StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)
Group: StrataFrame Developers
Posts: 3K, Visits: 2.5K
OK, here's the fix that now properly includes the _ORG pk value in the update sproc.
Attachments
ddt.zip (180 views, 750.00 KB)
StrataFrame Team
S
StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)StrataFrame Developer (3.5K reputation)
Group: StrataFrame Developers
Posts: 3K, Visits: 2.5K
OK, looks like this is a DDT problem... it should be adding PK_ORG to the parameter list, just in case anyone wants to change their primary key on a record (which they can since it's not an IDENTITY column... if you want to change it you might have a design problem, but by allowing this, we cover all of the bases).  I'll fix the DDT and post the update here (there seems to be a lot of DDT fixes in the last few days Wink).
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