<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Field length changes unintentionally when defining a composite key made of multiple non-consecutive fields"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=138238">138238</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Field length changes unintentionally when defining a composite key made of multiple non-consecutive fields
</td>
</tr>
<tr>
<th>Product</th>
<td>LibreOffice
</td>
</tr>
<tr>
<th>Version</th>
<td>6.4.6.2 release
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>UNCONFIRMED
</td>
</tr>
<tr>
<th>Severity</th>
<td>minor
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Base
</td>
</tr>
<tr>
<th>Assignee</th>
<td>libreoffice-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>algonzal@uji.es
</td>
</tr></table>
<p>
<div>
<pre>Description:
I faced this problem when creating a table in design mode with multiple columns
and different column types (more concretely, field lengths). Composite is made
of multiple columns, with columns in between composite key members (composite
key made of non-consecutive fields). If all fields are consecutive everything
works as expected.
The issue shows up in LO v6.4.6.2 (Linux), v6.4.7.2 (Windows 10, fresh install)
and v7.0.3.1 (again, Windows 10 fresh install). Using Java 8 (251). All systems
are 64 bits.
Steps to Reproduce:
1. Create a new database.
2. Create a new table in design mode (do not save it).
3. Define a column (e.g. name it "col1", name does not matter) with VARCHAR
type and length restricted to 9 characters.
4. Define another column (e.g. name it "col2", again, name does not matter)
with SMALLINT type.
5. Define another column (e.g. name it "col3") with FLOAT type.
6. Define another column (e.g. name it "col4") with TINYINT type.
7. Select columns: col1, col2 and col4 (skipping col3), in that concrete order
(when selecting them in reverse order, it works without issues).
8. Mark the 3 selected fields as primary key (composite key).
9. Check col1 length, it is 3, instead of 9.
Actual Results:
The length of col1 is 3, which matches the length of the last selected field.
When selecting columns in reverse order it is 9 (because it picks the length of
the latest selected column).
Expected Results:
The length of the first column should remain unchanged (9) after defining the
composite key of the table.
Reproducible: Always
User Profile Reset: No
Additional Info:
Version: 6.4.7.2 (x64)
Build ID: 639b8ac485750d5696d7590a72ef1b496725cfb5
CPU threads: 24; OS: Windows 10.0 Build 19041; UI render: default; VCL: win;
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded</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>