<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=121210#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=121210">bug 121210</a>
from <span class="vcard"><a class="email" href="mailto:robert@familiegrosskopf.de" title="robert@familiegrosskopf.de">robert@familiegrosskopf.de</a>
</span></b>
<pre>(In reply to Drew Jensen from <a href="show_bug.cgi?id=121210#c1">comment #1</a>)
<span class="quote">> Setting the field to Integer(Autovalue) which becomes an IDENTITY would also
> automatically create that PK.
>
> In the case of importing from a Calc this could lead rows with duplicate
> values in the Calc column not importing.</span >
If you could create a primarykey for a field you couldn't import a Calc-table
with duplicate values. This is independent of AutoValue "yes" or "no". The
import would fail. So the bug is: primarykey could be created and AutoValue
could not.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>