(I wanted to capture this for posterity but I'll admit I'm not sure it's worth maintaining the added complexity unless imports are going to become a more common thing.)

I've already done my production import so I'm not going to re-write all of my scripts to test, but I think the insert vs save trick look reasonable for IDs and creation dates.

I went to code up your suggestion with hasExplicitDateModified but I'm unsure why an extra field is needed at all. Why can't we use the same check as with dateCreated and end up with :

protected function willSaveObject() {
  $use_timestamps = $this->getConfigOption(self::CONFIG_TIMESTAMPS);

  if ($use_timestamps) {
    if (!$this->getDateCreated()) {
      $this->setDateCreated(time());
    }
    if (!$this->getDateModified()) {
      $this->setDateModified(time());
    }
  }

  if ($this->getConfigOption(self::CONFIG_AUX_PHID) && !$this->getPHID()) {
    $this->setPHID($this->generatePHID());
  }
}

That would give dateModified behavior identical to dateCreated. Specifically, the second time an object was saved, the dateModified would not be updated.

Hello,

may a example is available for this use case?

I want to use

CONFIG_IDS = IDS_MANUAL

and

CONFIG_TIMESTAMPS = false

.

Can I use the LISKDao for this like

protected function getConfiguration() {
    return array(
      self::CONFIG_IDS                      => self::IDS_MANUAL,
      self::CONFIG_TIMESTAMPS               => false,
    );
}

?

How can I use now maniphest.edit with arcanist? Is there a transaction for the manual ID available? How can I test this with the conduit console?

Best and thanks a lot