Re: Stored Procedure And Corsor
> The scrolling logic in a perl module and the existing functionality
> fails when it hits multiple instances of the same lastname.
Right, scrolling needs to be PK-aware.
> I have not written a stored procedure for 15 years
I don't see a need for one here. SQL Server is in a way built for sprocs, so it emphasises them. MySQL isn't and doesn't.
> HANDLER tbl_name READ index_name
Essentially Handler bypasses the relational database layer entirely. Terrible idea for scrolling. It's there for those rare occasions where EF Codd's fundamental "no back doors" rule needs to be briefly violated for a special purpose. Scrolling isn't such a purpose.
Subject
Views
Written By
Posted
3251
March 30, 2018 05:23AM
3057
March 30, 2018 10:20AM
1449
March 30, 2018 10:56AM
Re: Stored Procedure And Corsor
2674
March 30, 2018 12:45PM
2123
March 30, 2018 01:53PM
1201
March 30, 2018 02:04PM
2106
March 31, 2018 07:25PM
1293
March 31, 2018 08:00PM
3263
April 01, 2018 05:27PM
2079
April 02, 2018 09:48AM
1344
March 30, 2018 12:35PM
Sorry, you can't reply to this topic. It has been closed.
This forum is currently read only. You can not log in or make any changes. This is a temporary situation.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.