Uploaded image for project: 'Engineering'
  1. Engineering
  2. ENG-753

Allow private final SQLStmts in procedures or fix misleading error message

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: V1.2
    • Fix Version/s: V1.2
    • Component/s: Core
    • Labels:
      None

      Description

      Declaring a private final statement produces the incorrect error at run time (not project compile time):

      // check if the statement has been oked by the compiler/loader
      if (stmt.catStmt == null) {
      String msg = "SQLStmt objects cannot be instantiated after";
      msg += " VoltDB initialization. User may have instantiated a SQLStmt";
      msg += " inside a stored procedure's run method.";

      We should reflect on private SQLStmts and just make this work. I believe getDeclaredFields() will return private members which can be examined via reflection.

        Attachments

          Activity

            People

            • Assignee:
              jhugg John Hugg
              Reporter:
              rbetts Ryan Betts
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support