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

Re: [libreoffice-users] Base/Firebird Queries broken


Before I forget - the files used for to gather these runtime numbers are
found here:
https://gerrit.libreoffice.org/#/admin/projects/benchmark

There are five xls files with an explanation as to what the spreadsheet is
evaluating.

They are 4 years old it looks like but seem to be as good as I've found for
example files for this feature.

Seems to me it might be worthwhile to offer them for download (maybe as a
zip file) and reference that download location in the video and/or
associated posting text.

On Wed, Jan 16, 2019 at 1:06 PM Drew Jensen <drewjensen.inbox@gmail.com>
wrote:

> So, can you open that Query definition, the one that raised the error when
> you double clicked on it, in design view and Run it and it works?
>
> Is that what you are saying?
>
> Thanks
>
>
> On Wed, Jan 16, 2019 at 12:17 PM Paul D. Mirowsky <p_mirowsky@bentaxna.com>
> wrote:
>
>> Ok, things are narrowing down on this issue.
>>
>> I have a Query Design view in which I have a field Series set to 134.
>>
>> I remove the 134 and press enter.
>>
>> Run Query (F5)
>>
>> It works.
>>
>> Add back in 134 to Series field.
>>
>> It works
>>
>> Save it and save the database.
>>
>> Double click on the query to run it.
>>
>> Result in:
>>
>> > Error code: 1
>> >
>> > firebird_sdbc error
>> > *Dynamic SQL Error
>> > *SQL error code = -104
>> > *Invalid usage of boolean expression
>> > caused by
>> > 'isc_dsql_prepare'
>> It appears that the run function is adding an operation that is not in
>> Query Design view.
>>
>> Any suggestions?
>>
>> Thanks
>>
>> Paul
>>
>>
>> On 1/15/2019 6:19 PM, Paul D. Mirowsky wrote:
>> > I am receiving the following error when opening a query.
>> >
>> >> firebird_sdbc error:
>> >> *Dynamic SQL Error
>> >> *SQL error code = -104
>> >> *Invalid usage of boolean expression
>> >> caused by
>> >> 'isc_dsql_prepare'
>> > The table names are: Amps Volts-High
>> >
>> > The two tables involved both have one boolean field each, so I removed
>> > them from the query. The error still occurs.
>> >
>> > I am taking this to mean that there is a boolean comparison happening
>> > that is not in the SQL generated by Base.
>> >
>> > Is this possible?
>> >
>> > Thanks
>> >
>> > Paul
>> >
>> >
>> >
>>
>> --
>> 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
>>
>

--
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

Follow-Ups:
Re: [libreoffice-users] Base/Firebird Queries brokenDrew Jensen <drewjensen.inbox@gmail.com>
References:
[libreoffice-users] Base/Firebird Queries broken"Paul D. Mirowsky" <p_mirowsky@bentaxna.com>
Re: [libreoffice-users] Base/Firebird Queries broken"Paul D. Mirowsky" <p_mirowsky@bentaxna.com>
Re: [libreoffice-users] Base/Firebird Queries broken"Paul D. Mirowsky" <p_mirowsky@bentaxna.com>
Re: [libreoffice-users] Base/Firebird Queries brokenDrew Jensen <drewjensen.inbox@gmail.com>
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.