When I get a connection to the adressbook of Mac OS X I see the right date in the birthday-column. It is formatted in the table as "timestamp". Now I try to make a query in Base. Not birthday is shown. The field is formatted as text. It could not be formatted as date.
Created attachment 62456 [details] Shows birthdate (German: Geburtstag) as timestamp in tables and text in queries
The data itself are present in the query - sort by date i.e. works fine. There is just no display of the values. Formatting of the column is not possible, the only value shown in format-Dialog is "Text" and "@"
Hmm, I don't have a birthday field in my OSX address book to be able to compare... Alex
At least, not in the French version of Contacts.app and this consequently does not appear in my LO MacAb ODB connection. Alex
(In reply to comment #4) > At least, not in the French version of Contacts.app and this consequently > does not appear in my LO MacAb ODB connection. > > Alex Contacts.app V7.1(1170)
Is this some kind of personalized field that you added, or is it the default ?
OK, I could reproduce the problem with any of the Creation or Modification date fields. These are also indicated as timestamp, yet they show up blank in a query. How to reproduce : 1) Create an ODB file that connects to the Mac addressbook using the db creation wizard. 2) Open the ODB and the GUI query designer wizard. 3) Choose FirstName, Creation and Modification as the fields for display. 4) Validate or run query - only the FirstName field shows any data despite data being available in the Table view mode. The SQL that is displayed : SELECT "Address Book"."Prénom" AS "Prénom", "Address Book"."Creation" AS "Creation", "Address Book"."Modification" AS "Modification" FROM "Address Book" "Address Book" Note that despite specifically querying on 3 fields, 2 of which are timestamp type, only one timestamp field gets displayed and no data is shown for this field. Adding Lionel, Julien to CC. Alex
Is this a problem with the Mork driver ? Alex
I tested in LO 4.1.1.2 I can not create a connection to a MacAB with LO-dev 4.2, it systematically causes a crash of the whole app, but will report that separately. Alex
It also won't show a query that uses the ABPersonFlags field. These are defined as INT in Table design mode and yet do not show up in a query, so the problem seems to be that the Query parser or the returned display fails to handle anything other than CHAR datatype. Alex
Changed title to reflect findings
I tried to compare these files: http://opengrok.libreoffice.org/xref/core/connectivity/source/drivers/mork/MDatabaseMetaData.cxx#894 http://opengrok.libreoffice.org/xref/core/connectivity/source/drivers/macab/MacabDatabaseMetaData.cxx#807 http://opengrok.libreoffice.org/xref/core/connectivity/source/drivers/flat/EDatabaseMetaData.cxx#70 But don't get the logic for the moment. Alex: are you sure it's Mork driver which is used for Mac address book? (not Macab driver?)
(In reply to comment #12) > Alex: are you sure it's Mork driver which is used for Mac address book? (not > Macab driver?) I expect it is hte MacAB driver :)
(In reply to comment #13) > > I expect it is hte MacAB driver :) Lionel, I expect you're right, sorry :-) Alex
Adding self to CC if not already on
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT: - Update the version field - Reply via email (please reply directly on the bug tracker) - Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
The Query wizard returns an error : Query too complex The query designer UI returns a SYNTAX error using a date literal or a query too complex error when using > '31/12/2014' for example Version: 5.0.3.2 Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75 Locale : fr-FR (fr.UTF-8) OSX 10.11.2
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Still present Version: 6.1.0.0.alpha0+ Build ID: a488c7ad2763b944713997911c1ddb0315d8c93f CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-03-26_00:38:29 Locale: en-US (en_US.UTF-8); Calc: group
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present in Version: 6.2.2.2 Build ID: 2b840030fec2aae0fd2658d8d4f9548af4e3518d Threads CPU : 8; OS : Mac OS X 10.14.3; UI Render : par défaut; VCL: osx; Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded Make a query on just the Modification date field (this is defined as timestamp). An empty grid control is displayed with neither field entry (column header), nor any data.
Alex: just for curiosity, if you're launching LO from console, are there any useful information? Also taking a look at https://opengrok.libreoffice.org/xref/core/connectivity/source/drivers/macab/MacabDatabaseMetaData.cxx?r=48314f25#763, what official source do we have to confirm precision, max scale, etc for TIMESTAMP but also for other types? Indeed, we know that timestamp is kABDateProperty (see https://opengrok.libreoffice.org/xref/core/connectivity/source/drivers/macab/macabutilities.hxx?r=00657aef#123) and this last one is NSDate (see https://developer.apple.com/documentation/addressbook/address_book_objective-c_constants/property_types) but we'd need to know internals of NSDATE.
Dear Robert Großkopf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I'm still blocked from testing this due to bug 126961
Dear Robert Großkopf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Couldn't say anything about this bug. Have only written the bug description for another person. No Mac available here…
Bug still present in Version: 7.5.1.2 (AARCH64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Mac OS X 13.3.1; UI render: Skia/Raster; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded
Created attachment 186887 [details] LLdb output FWIW, here is the LLDB output when loading the ODB file that connects to the Contacts.app data source, and what is displayed in the termina when attempting to execute a query containing non-Char field types.
(In reply to Alex Thurgood from comment #28) > Created attachment 186887 [details] > LLdb output > > FWIW, here is the LLDB output when loading the ODB file that connects to the > Contacts.app data source, and what is displayed in the termina when > attempting to execute a query containing non-Char field types. There seems to be a whole lot of wrong things going on here : warn:legacy.osl:11240:267069:dbaccess/source/core/api/SingleSelectQueryComposer.cxx:874: OSingleSelectQueryComposer::getColumns: inconsistent column counts, this might result in wrong columns! and warn:comphelper:11240:267069:comphelper/source/misc/types.cxx:48: conversion from Any to sal_Int32 failed probably do not help the situation.
Patrick: on https://developer.apple.com/documentation/addressbook, there's: "Do not use the AddressBook framework in macOS 10.11 and later. Use the APIs defined in the Contacts framework instead." I suppose it means there's no need to investigate here, the macab driver ( connectivity/source/drivers/macab) should be rewritten from scratch to use "Contacts framework"?