Uploaded image for project: 'ActiveObjects'
  1. ActiveObjects
  2. AO-197

Warn on export when too long column data is encountered

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Obsolete
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      AO currently exports the data it finds in the DB as-is, without checking whether the data contained in the tables is actually valid. Importing of said export then fails with a "value too big for column" message.

      In my opinion the culprit here is HSQL, which does not enforce column constraints properly:
      "HSQLDB databases are initially created in a legacy mode that does not enforce column size and precision."
      see http://www.hsqldb.org/doc/guide/ch09.html#create_table-section

      I propose adding a warning in the export mentioning that/what invalid data was exported and that the export will most likely have to be cleaned up before import.

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            jnolen Jonathan Nolen added a comment -

            Pretty sure this issue is now obsolete since we are specifiying/enforcing column lengths more aggressively.

            Show
            jnolen Jonathan Nolen added a comment - Pretty sure this issue is now obsolete since we are specifiying/enforcing column lengths more aggressively.

              People

              • Assignee:
                Unassigned
                Reporter:
                miruflin Michael Ruflin
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Who's Looking?