Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-14459

street parsing fatals rather than graceful error when it mis-assigns values to street_unit

    Details

    • Type: Bug
    • Status: Done/Fixed
    • Priority: Trivial
    • Resolution: Fixed/Completed
    • Affects Version/s: 4.4.4
    • Fix Version/s: 4.5
    • Component/s: None
    • Labels:
      None

      Description

      I've hit this twice in 2 days - when the address somehow doesn't
      parse right either the contact can't be saved or the job.geocode script crashes e.g

      drush cvapi job.geocode parse=1 geocoding='false'
      Array
      (
      [error_code] => unknown error
      [sql] => UPDATE civicrm_address SET street_number = 267 , street_number_su ffix = NULL , street_name = 'C' , street_unit = 'aptain Bob Smith Rd' WHERE ( civicrm_address.id = 2555 ) [nativecode=1406 ** Data too long for column 's treet_unit' at row 1]
      [tip] => add debug=1 to your API call to have more info about the error
      [is_error] => 1
      [error_message] => DB Error: unknown error
      )

        Attachments

          Activity

            People

            • Assignee:
              colemanw Coleman Watts
              Reporter:
              eileen Eileen McNaughton
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: