Members of the KDE Community are recommended to subscribe to the kde-community mailing list at https://mail.kde.org/mailman/listinfo/kde-community to allow them to participate in important discussions and receive other important announcements

  1. 12 Jul, 2020 1 commit
  2. 08 Jul, 2020 1 commit
    • Friedrich W. H. Kossebau's avatar
      Find also Python3 with find_package(PythonInterp) · 3dd6893e
      Friedrich W. H. Kossebau authored
      At least with openSUSE TW searching with a version given seems to restrict
      the versions accepted to the major version.
      So if only python3 is available, searching for 2.6 yields no results.
      Given 2.6 is stone-age old, we can assume any found version is good enough
      these days.
      3dd6893e
  3. 26 Jun, 2020 2 commits
  4. 22 Jun, 2020 1 commit
  5. 18 Jun, 2020 2 commits
  6. 17 Jun, 2020 2 commits
  7. 10 Jun, 2020 1 commit
  8. 04 Jun, 2020 1 commit
  9. 30 May, 2020 2 commits
  10. 22 May, 2020 2 commits
  11. 17 May, 2020 2 commits
  12. 11 May, 2020 2 commits
  13. 10 May, 2020 2 commits
    • Jarosław Staniek's avatar
      b64a6248
    • jordi fita i mas's avatar
      Improve a bit parse error diagnosis · aa5f0648
      jordi fita i mas authored
      Summary:
      Currently, the parse error message for a query like
      
          SELECT select #1/1a/2020#;
      
      is
      
          org.kde.kdb.core: Parse error: tokens left globalCurrentPos: 18 sql.length(): 19 globalToken: ";"
          org.kde.kdb.core: error:
          org.kde.kdb.core: at character  18  near tooken  ";"
      
      and Kexi, in SQL text mode, moves the cursor next to the semicolon.
      
      The query is indeed incorrect, but the error message is misleading
      because the error is in the “a” within the date literal, not the
      terminating semicolon.
      
      This is due the lack of a “fallback” rule within the DATE_OR_TIME start
      condition and, because it is an exclusive condition, Flex provides its
      default rule that returns nothing to the parser. Therefore, the
      globalCurrentPos is not incremented and, at the end, KDbParser can
      detect something went wrong, but can not pinpoint the error’s correct
      location at that stage.
      
      I added a new rule that simply returns any unrecognized character as a scan
      error to the parser so that it can detect the erroneous input and present a
      more accurate position of where the error is. With that change Kexi moves the
      cursor next to the “a”.
      
      I also added the same rule to the INITIAL start condition to match any
      character, because otherwise it also reports the error at the position of the
      semicolon in queries like the following:
      
          SELECT 1' FROM input;
      
      When the unexpected character is one used for quoting (i.e., ', ", or `), the
      message avoid quoting the unexpected message because it is harder to read the
      error depending on the font.
      
      There was, however, another issue with Flex’s action for its default
      rule: it calls the ECHO macro that, by default, is defined as write the
      matched input to stdout.
      
      This is not a problem for Kexi — in fact, i am unable to see that write
      in the console —, but it messes up the output of SqlParseTest. This is
      particularly important when called with the ‘-xml’ or ‘-tap’ parameters,
      that need to maintain their strict format or then QtCreator or Perl’s
      prove can not parse the output.
      
      FIXED-IN:3.2.1
      
      Reviewers: staniek, piggz
      
      Reviewed By: staniek
      
      Subscribers: Kexi-Devel-list
      
      Tags: #kdb
      
      Differential Revision: https://phabricator.kde.org/D29327
      aa5f0648
  14. 03 May, 2020 2 commits
    • Jarosław Staniek's avatar
      098b196f
    • jordi fita i mas's avatar
      Escape table name in when building a select statement with row id · 14280f03
      jordi fita i mas authored
      Summary:
      When a KDbQuerySchema has a table name or alias that is a reserved SQL
      keyword, and the alsoRetrieveRecordId statement option is set to true,
      KDbNativeStatementBuilder constructed an incorrect statement.
      
      For instance, if trying to create a SELECT statement in SQLite of a
      table named “table” with a single “id column, the generated query was:
      
          SELECT [id], table.OID FROM [table] ORDER BY [id]
      
      The execution if that query generated an error due to the unescaped
      table keyword.  With this commit, the generated query is:
      
          SELECT [id], [table].OID FROM [table] ORDER BY [id]
      
      FIXED-IN:3.2.1
      
      Reviewers: staniek, piggz
      
      Reviewed By: staniek
      
      Subscribers: Kexi-Devel-list
      
      Tags: #kdb
      
      Differential Revision: https://phabricator.kde.org/D29277
      14280f03
  15. 25 Apr, 2020 4 commits
    • Jarosław Staniek's avatar
      33a978fe
    • jordi fita i mas's avatar
      Expand feature test for buffered cursors · 3e7b595e
      jordi fita i mas authored
      Summary:
      When testing a driver’s cached cursors it is interesting to see whether
      the cursor actually can go back to the first record and then return the
      values for all of them again.
      
      Checking only the return value of KDbCursor::moveFirst and
      KDbCursor::moveLast is not enough to see if it works, because they just
      return true even though the driver does not change anything.
      
      Reviewers: staniek, piggz
      
      Subscribers: Kexi-Devel-list
      
      Tags: #kdb
      
      FIXED-IN:3.2.1
      
      Differential Revision: https://phabricator.kde.org/D29185
      3e7b595e
    • Jarosław Staniek's avatar
      1632bda3
    • jordi fita i mas's avatar
      Take all args to kdbfeaturestest before the driver · 20fb7f0d
      jordi fita i mas authored
      Summary:
      kdbfeaturetest gave the following error when trying to test buffered
      cursors:
      
          > .//kdbfeaturestest --buffered-cursors --test cursors sqlite /tmp/cursor.test
          DRIVERS:  ("org.kde.kdb.postgresql", "org.kde.kdb.sqlite")
          org.kde.kdb.core: loading "org.kde.kdb.--buffered-cursors"
          KDbResult: CODE=10 MESSAGE="Could not find database driver \"org.kde.kdb.--buffered-cursors\"." SERVER_ERROR_CODE=0
          main: "cursors" test: ERROR
      
      kdbfeaturetest’s main tries to remove all arguments from args[] before
      using the first remaining string as the driver’s name, but the code that
      removes --buffered-cursors and --query-parameters was below the one for
      the driver. Therefore, it assumed that either of the two, since they
      where still in args, was the driver’s name.
      
      I just moved the two calls to take those parameters above the driver.
      
      FIXED-IN:3.2.1
      
      Reviewers: staniek, piggz
      
      Subscribers: Kexi-Devel-list
      
      Tags: #kdb
      
      Differential Revision: https://phabricator.kde.org/D29184
      20fb7f0d
  16. 05 Apr, 2020 1 commit
  17. 04 Apr, 2020 2 commits
  18. 28 Mar, 2020 1 commit
  19. 24 Mar, 2020 2 commits
  20. 01 Feb, 2020 2 commits
  21. 30 Nov, 2019 1 commit
  22. 29 Oct, 2019 4 commits