If I use the usual way of creating a table with editing it, I only find the data-typ "date/time". In the right property-table there is a sub-property of "date/time" = "time". Unfortunately this is not persistent. In this way its for now not possible to create time-fields. If I go the path "B" I create a table with LO, create a column (field) with "time" (example 15:00). Importing this as cvs, kexi recognizes the field really as "time" (!) but finally the import ends in a date. Am I right, that earlier versions of kexi worked better in this case? Somehow I remember. Reproducible: Always
Created attachment 98960 [details] during cvs-import
Created attachment 98961 [details] result in form
Created attachment 98962 [details] Result in report
Created attachment 98963 [details] result in form_new The image "result in form" must be replaced by the image "result in form_new"
*** Bug 371894 has been marked as a duplicate of this bug. ***
Regarding: > If I use the usual way of creating a table with editing it, I only find the > data-typ "date/time". In the right property-table there is a sub-property of > "date/time" = "time". Unfortunately this is not persistent. In this way its for > now not possible to create time-fields. I confirm this works as expected in 3.1 or even in 3.0. 2.9 can't be fixed. However this topic is not related to the summary of the bug report (Forms/report) so I will update the summary. I'll also test the CSV topic and create bug if needed. In the future it's better to keep on topic in one bug report -- here are three topics already if I understood them correctly.
Created attachment 117205 [details] Kexi 3.2: Importing CSV with date/time/date-time values
Created attachment 117206 [details] Resulting KEXI file: Imported CSV with date/time/date-time values
Created attachment 117207 [details] Imported CSV file with date/time values
Please find attachment from comments 7, 8, 9 to see evidence of support for proper date/time CSV import in KEXI 3.2. I think it was OK like this in 3.1.0 too after we fixed unrelated regression of https://bugs.kde.org/show_bug.cgi?id=386102.