Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-98471

[REG: 5->6.2.1] Null QDateTime is not stored as NULL anymore in Oracle OCI

    XMLWordPrintable

Details

    • 999d856bc8 (qt/qtbase/dev) 999d856bc8 (qt/tqtc-qtbase/dev) d2e8310680 (qt/qtbase/6.2.3) d2e8310680 (qt/tqtc-qtbase/6.2.3) 2d7c19fde2 (qt/qtbase/6.3) 2d7c19fde2 (qt/tqtc-qtbase/6.3) 3474ae0d40 (qt/qtbase/6.2) 3474ae0d40 (qt/tqtc-qtbase/6.2)

    Description

      In Qt 5.14 at least, passing QDateTime() to bindValue() ended up as NULL in the database. Now in Qt 6, it instead seems to be able to produce invalid datetime entry in the database (and not null).

      After running such insert, the new row in the database is showing invalid date ('00.00.0000').

      Attachments

        1. qtbug98471.zip
          0.8 kB
          Joni Poikelin

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-99408 [SQL] The SQL driver for Firebird/Interbase does not unpack the QVariant before null check

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              vhilshei Volker Hilsheimer
              poikelin Joni Poikelin
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: