<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - FIREBIRD : Migration : error on importing tables or queries with names longer than 30 characters" href="https://bugs.documentfoundation.org/show_bug.cgi?id=116987#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - FIREBIRD : Migration : error on importing tables or queries with names longer than 30 characters" href="https://bugs.documentfoundation.org/show_bug.cgi?id=116987">bug 116987</a> from <a class="email" href="mailto:iplaw67@tuta.io" title="Alex Thurgood <iplaw67@tuta.io>"> Alex Thurgood</a> <pre>(In reply to Tamas Bunth from <a href="show_bug.cgi?id=116987#c7">comment #7</a>) > A workaround would be to truncate table names with more than 30 characters. > Not really a very satisfactory one though from a user perspective. The whole point of being able to uniquely identify a table in hsqldb with a "long" file name has clearly been used by DBAs and users alike. On the one hand, imposing a new form of table naming as you suggest isn't going to go down well with those users unless there is a valid reason, which there doesn't seem to be given that in FB4 that limitation will be lifted (but of course when that might happen is a different matter). On the other hand, one could submit that having table names in excess of 30 characters really isn't the way one should be managing a DB in the first place, but that is a debate for another day. Would it not be better to simply abort with a more meaningful message than is currently offered, something along the lines of : "Firebird 3 doesn't currently support table/query/view names of more than 30 characters, please shorten your table names in the original file and try again."</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>