<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - EDITING: Query input in foreignkey-field impossible, when two tables in the query." href="https://bugs.documentfoundation.org/show_bug.cgi?id=68153#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - EDITING: Query input in foreignkey-field impossible, when two tables in the query." href="https://bugs.documentfoundation.org/show_bug.cgi?id=68153">bug 68153</a> from <a class="email" href="mailto:lionel@mamane.lu" title="Lionel Elie Mamane <lionel@mamane.lu>"> Lionel Elie Mamane</a> <pre>(In reply to Terrence Enger from <a href="show_bug.cgi?id=68153#c2">comment #2</a>) > That said, it would be good for Base, when it cannot accept an update, > either to disallow keystrokes in the cell (as it actually does under > some circumstances) Yes. In my testing (the default table control used when double-clicking on the query), it actually disallows keystrokes in t_ID, but allows them in town_ID. So the mechanism to not allow changes is definitely there, it is "just" used only on the side of the relation where the field is the primary key. It needs to be locked on both sides. Happy to take/review patches.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>