Answers

• kthorngren Posts: 22,159Questions: 26Answers: 5,100

  July 14

  In the Editor server libraries you can add .Debug(true) before .Process() to see the generated query. Use the browser's network inspector to view the JSON response. See the debug() docs for more details.

  This thread has that error and Allan has provided some troubleshooting steps. If the steps don't help then post the results of the troubleshooting steps.

  Kevin
• rwgreenwood Posts: 48Questions: 14Answers: 0

  July 14 edited July 14

  The message that is in the JSON response from the server is pasted below. The weird things is that I set my postgres server to log all statements, then pasted the query that it logged from the datatables request into pgAdmin and it ran without errors. Similarly, the query in the error message below works in pgAdmin. So it's not a matter of invalid SQL.

  {
      "fieldErrors": [],
      "error": "An SQL error occurred: SQLSTATE[25P02]: In failed sql transaction: 7 ERROR:  current transaction is aborted, commands ignored until end of transaction block",
      "data": [],
      "ipOpts": [],
      "cancelled": [],
      "debug": [
          "Editor PHP libraries - version 2.2.2",
          {
              "query": "SELECT  \"reservations\".\"id\" as \"reservations.id\", \"reservations\".\"day\" as \"reservations.day\", \"reservations\".\"trip_type\" as \"reservations.trip_type\", \"reservations\".\"segment\" as \"reservations.segment\", \"reservations\".\"craft\" as \"reservations.craft\", \"reservations\".\"launch_time\" as \"reservations.launch_time\", \"reservations\".\"take_out_time\" as \"reservations.take_out_time\", \"reservations\".\"client_name\" as \"reservations.client_name\", \"reservations\".\"client_info\" as \"reservations.client_info\", \"reservations\".\"canceled\" as \"reservations.canceled\", \"reservations\".\"members_id\" as \"reservations.members_id\", \"reservations\".\"notes\" as \"reservations.notes\", \"reservations\".\"allocated\" as \"reservations.allocated\", \"reservations\".\"released_allocation\" as \"reservations.released_allocation\", \"reservations\".\"pending\" as \"reservations.pending\", \"reservations\".\"fee_charged\" as \"reservations.fee_charged\", \"reservations\".\"retref\" as \"reservations.retref\", \"reservations\".\"checked_in\" as \"reservations.checked_in\", \"reservations\".\"at_launch\" as \"reservations.at_launch\", \"reservations\".\"boat_license\" as \"reservations.boat_license\", \"reservations\".\"created\" as \"reservations.created\", \"members\".\"username\" as \"members.username\", \"members\".\"id\" as \"members.id\", \"trip_types\".\"name\" as \"trip_types.name\", \"segments\".\"name\" as \"segments.name\" FROM  \"reservations\" LEFT JOIN \"members\" ON \"members\".\"id\" = \"reservations\".\"members_id\"  LEFT JOIN \"trip_types\" ON \"trip_types\".\"id\" = \"reservations\".\"trip_type\"  LEFT JOIN \"segments\" ON \"segments\".\"id\" = \"reservations\".\"segment\" WHERE \"members_id\" = :where_0 AND  \"reservations\".\"day\" = :where_1 AND (\"canceled\" IS NULL OR  \"canceled\" > :where_4 )",
              "bindings": [
                  {
                      "name": ":where_0",
                      "value": "44",
                      "type": null
                  },
                  {
                      "name": ":where_1",
                      "value": "2025-7-14",
                      "type": null
                  },
                  {
                      "name": ":where_4",
                      "value": "2025-07-13 20:00",
                      "type": null
                  }
              ]
          },
          {
              "query": "SELECT DISTINCT  \"id\" as \"id\", \"name\" as \"name\" FROM  \"trip_types\" ",
              "bindings": []
          },
          {
              "query": "SELECT DISTINCT  \"id\" as \"id\", \"name\" as \"name\" FROM  \"segments\" ",
              "bindings": []
          }
      ]
  }
  
• allan Posts: 64,743Questions: 1Answers: 10,713 Site admin

  July 14

  2.2.2 is a bit out of date. It would be worth updating the server-side libraries to 2.4.3which you can get from npm or here. I'm not immediately aware of a fix that has gone in, but its always worth trying the latest .

  I'll try updating my libpq and seeing what happens, hopefully tomorrow.

  Allan
• rwgreenwood Posts: 48Questions: 14Answers: 0

  July 14

  This is looking more and more like a server configuration issue, not a datatables issue. I don't want to create unnecessary noise on this forum (but I do appreciate any suggestions). The server where the issue turned up is running postgres 15 and showed a libpq version change of 17.2 to 17.5. However when I test on a server with libpg version of 17.0.

  The server with libpq 17.2 to 17.5 is using the apt.postgresql.org repo. The server with libpq 17.0 is using the standard Ubuntu 24.04 repo.
• rwgreenwood Posts: 48Questions: 14Answers: 0

  July 15

  I meant to say that when I test on a server with libpg 17.0 all is good.
• allan Posts: 64,743Questions: 1Answers: 10,713 Site admin

  July 15

  I'm not immediately seeing anything at this end unfortunately. Could you try adding:

  ->transaction(false)
  

  immediately before the ->process(...) call and see if that provides any extra information? It isn't ideal, as you do want transactions for rolling back, but I wonder if it might tell us a little more about what is going on.

  Allan
• rwgreenwood Posts: 48Questions: 14Answers: 0

  July 16

  I'm closing this thread, at least for the time being. The issue exists on only one computer which is in production and which I have limited ability to do trouble shooting on. Thank you very much for the replies, they have been helpful.
• allan Posts: 64,743Questions: 1Answers: 10,713 Site admin

  July 17

  Okay - thanks for the update. Let me know if you find out what is wrong with that specific machine - I'm curious

  Allan