[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-users] Table fields from Mariadb to Base

On 7/16/19 1:54 PM, Harvey Nimmo wrote:
I am connecting a Base client (Version: to a remote mariadb
using the MySQL (JDBC) connector.

A form I had generated in Base needed a new field that had to be added
to the source (Base) query and the related (Mariadb) table.

Having added the new field to the table using the Base client, I
expected it to appear in the query which is of the form (SELECT * FROM
<tablename>). It didn't until I closed Base and restarted it.

Is this a bug? Known or new?

Best Regards


I did not have any problem with this. I did this:

1) Created a new query from a current table in my database, Commentary. Use SQL, I added
        SELECT * FROM `Bible`.`Commentary` `Commentary`

2) Added a field to Commentary table.

3) Saved the table.

4) Saved the database. (Did you do this?)

5)I opened the query. (If your query was already open, you should have clicked the Run button.)


To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy

[libreoffice-users] Table fields from Mariadb to BaseHarvey Nimmo <harvey@nimmo.de>
Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.