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

Fix DAO failure to save to timestamp fields

          Details

          • Type: Bug
          • Status: Done/Fixed
          • Priority: Trivial
          • Resolution: Fixed/Completed
          • Affects Version/s: 4.6.2
          • Fix Version/s: 4.7
          • Component/s: None
          • Labels:
            None
          • Documentation Required?:
            Developer Doc
          • Funding Source:
            Needs Funding

            Description

            The DAO currently won't save timestamp fields. The code blocks it with a comment that indicates it doesn't make sense. However, Tim & I agree that the comment is the one that doesn't make sense

            It appears to be based on an incorrect assumption that timestamps are only managed by MYSQL methods & predates the apiv3 & apiv2

              Attachments

                Issue Links

                supplements

                Bug - A problem which impairs or prevents the functions of the product. CRM-20178 Writes to timestamp fields are silently ignored by $dao->save()

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Done/Fixed

                  Activity

                    People

                    • Assignee:
                      timotten Tim Otten
                      Reporter:
                      eileen Eileen McNaughton
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      2 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved: