<p>In <a href="https://github.com/dbsrgits/dbix-class/pull/88#discussion_r43756457">lib/DBIx/Class/ResultSource.pm</a>:</p>
<pre style='color:#555'>&gt; @@ -724,6 +725,11 @@ This will result in a unique constraint named
&gt;  C&lt;table_column1_column2&gt;, where C&lt;table&gt; is replaced with the table
&gt;  name.
&gt;  
&gt; +The &quot;extra&quot; hashref will be passed to
</pre>
<p>It's not an <code>extra hashref</code> anymore. User specifies explicit <code>uc_name =&gt; { extra =&gt; &lt;what will go to SQLT&gt;, &lt;other options&gt; }</code>. This way you keep the API extensible in the future, instead of locking things into <em>all of this will be passed to SQLT and you better hope it interoperates forever, KTHXBAI!</em></p>

<p>In fact I would call it <code>sqlt_extra</code> (even though there is precedent in <a href="https://metacpan.org/pod/DBIx::Class::ResultSource#extra">https://metacpan.org/pod/DBIx::Class::ResultSource#extra</a>, but that's arguably bad precedent)</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br>Reply to this email directly or <a href="https://github.com/dbsrgits/dbix-class/pull/88/files#r43756457">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AASeAnXHk6UgPsQPAePoqgCV7gidCBwGks5pCMKZgaJpZM4Ga5rQ.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/88/files#r43756457"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>