Menu

#263 One FETCH is necessary for UPDATE/DELETE WHERE CURRENT OF

Development Queue
open
5
2013-06-12
2011-12-20
Abbas Butt
No

In PG UPDATE/DELETE WHERE CURRENT OF work even if no row has been fetched from the cursor, in XC at least one FETCH is necessary.
This limitation is because of the way cursors are implemented in XC.

The test case involved here is portals.sql.

Discussion

  • Abbas Butt

    Abbas Butt - 2012-03-06
    • milestone: --> 2663467
     
  • Abbas Butt

    Abbas Butt - 2012-03-10
    • milestone: 2663467 --> 2663488
     
  • Koichi Suzuki

    Koichi Suzuki - 2012-03-12

    PG document says we need at least one fetch to WHERE CURRENT OF. In reality, PG allows WHERE CURRENT OF without fetching any.

    May consider to write this explicitly in some of the documents.

     
  • Koichi Suzuki

    Koichi Suzuki - 2012-03-12
    • milestone: 2663488 --> 2663467
     
  • Koichi Suzuki

    Koichi Suzuki - 2012-06-03
    • assigned_to: nobody --> gabbasb
     
  • Koichi Suzuki

    Koichi Suzuki - 2012-09-12

    This is specific notice for XC that application should FETCH first to update/delete WCO. Documentation update is required and leave this as XC specific.

    Q3: would like to be included in the next minor release.

     
  • Koichi Suzuki

    Koichi Suzuki - 2013-03-12
    • milestone: 2663467 --> 5139567
     
  • Koichi Suzuki

    Koichi Suzuki - 2013-06-12
    • milestone: 5139567 --> Development Queue
     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.