<p>Ok, given the clusterfuck the best solution I could come up with is <a href="https://github.com/dbsrgits/dbix-class/blob/11f335cd/t/icdt/engine_specific/sybase.t#L126-L134">this workaround</a>. I made it into a test so it is exercised going forward. Refer to the <a href="https://github.com/dbsrgits/dbix-class/commit/11f335cd8">commit message</a> for the gory details (though you already know most of them).</p>

<p>I do not have a more general solution in mind, short of "just make a new set of inflators/datetime_setup routines for the affected storages". </p>

<p>This is more or less the limit of what the current misdesigned system can do :/</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly or <a href="https://github.com/dbsrgits/dbix-class/pull/84#issuecomment-209291527">view it on GitHub</a><img alt="" height="1" src="https://github.com/notifications/beacon/AASeAtXU8812g0A06Pa0TBgpnHGrysIKks5p3KHbgaJpZM4Frnv5.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/dbsrgits/dbix-class/pull/84#issuecomment-209291527"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>