[jira] [Closed] (EMPIREDB-417) DBCommand Feature Request: add WHERE without overwriting

[ https://issues.apache.org/jira/browse/EMPIREDB-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz closed EMPIREDB-417. - Resolution: Won't Fix > DBCommand Feature Request: add WHERE without overwrit

[jira] [Commented] (EMPIREDB-417) DBCommand Feature Request: add WHERE without overwriting

[ https://issues.apache.org/jira/browse/EMPIREDB-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829448#comment-17829448 ] Jan Glaubitz commented on EMPIREDB-417: --- WHERE CREATE_USER IN (1, 2, 3, 4, 5) AND CREATE_USER = 1

[jira] [Created] (EMPIREDB-417) DBCommand Feature Request: add WHERE without overwriting

Jan Glaubitz created EMPIREDB-417: - Summary: DBCommand Feature Request: add WHERE without overwriting Key: EMPIREDB-417 URL: https://issues.apache.org/jira/browse/EMPIREDB-417 Project: Empire-DB

[jira] [Resolved] (EMPIREDB-415) DataListEntry.hasField / DataListHead.getColumnIndex

[ https://issues.apache.org/jira/browse/EMPIREDB-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz resolved EMPIREDB-415. --- Resolution: Won't Fix > DataListEntry.hasField / DataListHead.getColumnIn

[jira] [Comment Edited] (EMPIREDB-415) DataListEntry.hasField / DataListHead.getColumnIndex

[ https://issues.apache.org/jira/browse/EMPIREDB-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808055#comment-17808055 ] Jan Glaubitz edited comment on EMPIREDB-415 at 1/18/24 7:48 AM: Hi

[jira] [Commented] (EMPIREDB-415) DataListEntry.hasField / DataListHead.getColumnIndex

[ https://issues.apache.org/jira/browse/EMPIREDB-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808055#comment-17808055 ] Jan Glaubitz commented on EMPIREDB-415: --- Hi Rainer, sure, I found a workaround myself. But I

[jira] [Comment Edited] (EMPIREDB-415) DataListEntry.hasField / DataListHead.getColumnIndex

[ https://issues.apache.org/jira/browse/EMPIREDB-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807746#comment-17807746 ] Jan Glaubitz edited comment on EMPIREDB-415 at 1/17/24 2:51 PM: Hi

[jira] [Commented] (EMPIREDB-415) DataListEntry.hasField / DataListHead.getColumnIndex

[ https://issues.apache.org/jira/browse/EMPIREDB-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807746#comment-17807746 ] Jan Glaubitz commented on EMPIREDB-415: --- Hi Rainer, yes, the TRUE case works. The fallback is my

[jira] [Updated] (EMPIREDB-415) DataListEntry.hasField / DataListHead.getColumnIndex

[ https://issues.apache.org/jira/browse/EMPIREDB-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz updated EMPIREDB-415: -- Issue Type: Bug (was: Improvement) > DataListEntry.hasField / DataListHead.getColumnIn

[jira] [Created] (EMPIREDB-415) DataListEntry.hasField / DataListHead.getColumnIndex

Jan Glaubitz created EMPIREDB-415: - Summary: DataListEntry.hasField / DataListHead.getColumnIndex Key: EMPIREDB-415 URL: https://issues.apache.org/jira/browse/EMPIREDB-415 Project: Empire-DB

re: Problem inserting LocalTime to TIME Columns

eturn "convert(time, '{0}')"; > > The example is taken from the SQL-Server implementation (DBMSHandlerMSSQL). > > Please check. > Regards > Rainer > > P.S. Please consider creating a Jira ticket yourself next time. Thanks. > > > -Original Me

Re: Problem inserting LocalTime to TIME Columns

Can anyone confirm or deny this is a bug? Thanks, jan > Am 14.07.2023 um 09:51 schrieb Jan Glaubitz : > > Hi, > > I want to insert LocalTime objects into DataType.TIME-columns. > > Empire-db: > > [...] > this.ABFAHRT_PLAN = addColumn("ABFAH

Problem inserting LocalTime to TIME Columns

Hi, I want to insert LocalTime objects into DataType.TIME-columns. Empire-db: [...] this.ABFAHRT_PLAN = addColumn("ABFAHRT_PLAN", DataType.TIME, 0.0, false); this.ABFAHRT_IST = addColumn("ABFAHRT_IST", DataType.TIME, 0.0, false); [...] PostgreSQL: [...] ABFAHRT_PLAN TIME, ABFAHRT_IST

[jira] [Resolved] (EMPIREDB-413) Add support for PostgreSQL 'interval'

[ https://issues.apache.org/jira/browse/EMPIREDB-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz resolved EMPIREDB-413. --- Resolution: Fixed added in commit d77aa42edda661d7cf209b9fc77a59ea958e5772 {code:java

[jira] [Created] (EMPIREDB-413) Add support for PostgreSQL 'interval'

Jan Glaubitz created EMPIREDB-413: - Summary: Add support for PostgreSQL 'interval' Key: EMPIREDB-413 URL: https://issues.apache.org/jira/browse/EMPIREDB-413 Project: Empire-DB Issue Type

Re: [VOTE] Release Apache Empire-db 3.1.0 (rc1)

+1 > Am 14.04.2023 um 15:44 schrieb Rainer Döbele : > > Hi all, > > I am happy to announce that we have completed the preparation for our new > release Empire-db 3.1.0. > Thanks to all contributors for participating. > > I have prepared a release candidate (apache-empire-db-3.1.0-rc1) which

Re: Reminder: [VOTE] Release Apache Empire-db 3.1.0 (rc1)

+1 Von meinem iPhone gesendet > Am 17.04.2023 um 17:25 schrieb Rainer Döbele : > > Hi all, > > someone has reported that he has sent his vote but it does not appear on the > mailing list. > This is a check if the mailing list works properly. > > If anyone else has already sent his vote and

emire-jsf: formGrid mode="grid"

Hello, I just tested the new formGrid mode=„grid“. I think it’s a good idea to finally move away from table layouts. Can anyone provide an example CSS for a responsive form layout? E. g. label - value - label - value label - value - label - value for big screens and label - value label -

[jira] [Resolved] (EMPIREDB-397) PostgreSQL: Add support for websearch_to_tsquery

[ https://issues.apache.org/jira/browse/EMPIREDB-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz resolved EMPIREDB-397. --- Resolution: Fixed added in commit 86624c4a78c3fa9c8581c6399e30abaef1b21e52 > Postgre

[jira] [Created] (EMPIREDB-397) PostgreSQL: Add support for websearch_to_tsquery

Jan Glaubitz created EMPIREDB-397: - Summary: PostgreSQL: Add support for websearch_to_tsquery Key: EMPIREDB-397 URL: https://issues.apache.org/jira/browse/EMPIREDB-397 Project: Empire-DB

[jira] [Created] (EMPIREDB-392) e:input inside ui:repeat does not work

Jan Glaubitz created EMPIREDB-392: - Summary: e:input inside ui:repeat does not work Key: EMPIREDB-392 URL: https://issues.apache.org/jira/browse/EMPIREDB-392 Project: Empire-DB Issue Type

Re: [VOTE] Release Apache Empire-db 3.0.0 (rc1)

+1 Von meinem iPad gesendet > Am 08.03.2022 um 16:42 schrieb Rainer Döbele : > > Hi all, > > there has been a lot going on recently, and I am happy to announce, that > Empire-db 3.0.0 is ready for distribution. > Thanks to all contributors for participating. > > I have prepared a release

Re: Last call Empire-db v3 & Preview for new Website!

Hi Rainer, in DBRecordBase there is a deprecated method setValue(column, value). Why not drop it for version 3? Von meinem iPad gesendet > Am 03.03.2022 um 11:10 schrieb Rainer Döbele : > >  > Dear community, > > I am happy to announce, that we’re nearly there: IMO Empire-db version 3.0 is

[jira] [Resolved] (EMPIREDB-195) Review PostgreSQL driver's DDL generation for sequences

[ https://issues.apache.org/jira/browse/EMPIREDB-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz resolved EMPIREDB-195. --- Resolution: Fixed Sequence handling is improved in Empire-db 3.0. For PostgreSQL set

[jira] [Updated] (EMPIREDB-195) Review PostgreSQL driver's DDL generation for sequences

[ https://issues.apache.org/jira/browse/EMPIREDB-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz updated EMPIREDB-195: -- Fix Version/s: empire-db-3.0.0 Affects Version/s: empire-db-2.5.1 > Rev

[jira] [Assigned] (EMPIREDB-382) Provide easy access to native DBMS functions

[ https://issues.apache.org/jira/browse/EMPIREDB-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz reassigned EMPIREDB-382: - Assignee: Rainer Döbele (was: Jan Glaubitz) > Provide easy access to native D

[jira] [Assigned] (EMPIREDB-195) Review PostgreSQL driver's DDL generation for sequences

[ https://issues.apache.org/jira/browse/EMPIREDB-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz reassigned EMPIREDB-195: - Assignee: Jan Glaubitz > Review PostgreSQL driver's DDL generation for sequen

[jira] [Assigned] (EMPIREDB-382) Provide easy access to native DBMS functions

[ https://issues.apache.org/jira/browse/EMPIREDB-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz reassigned EMPIREDB-382: - Assignee: Jan Glaubitz > Provide easy access to native DBMS functi

Re: Last call Empire-db v3 & Preview for new Website!

Hi Rainer, thanks for your great work on version 3 and the new website. I just finished migrating my big webapp to Empire-db 3.0 using your migration guide. It was a little bit painful but I think it was worth it. I really like the new clean API. I like the new website, too. Its good to see

[jira] [Resolved] (EMPIREDB-378) PostgeSQL: SQL Pattern for TIMESTAMP Columns

[ https://issues.apache.org/jira/browse/EMPIREDB-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz resolved EMPIREDB-378. --- Resolution: Fixed changed in commit 572b3f0d41f6e13c408c62735cf714cc7b63e211 > Postge

[jira] [Created] (EMPIREDB-378) PostgeSQL: SQL Pattern for TIMESTAMP Columns

Jan Glaubitz created EMPIREDB-378: - Summary: PostgeSQL: SQL Pattern for TIMESTAMP Columns Key: EMPIREDB-378 URL: https://issues.apache.org/jira/browse/EMPIREDB-378 Project: Empire-DB Issue

[jira] [Resolved] (EMPIREDB-377) Page - addFacesMessage always issues WARN-Message

[ https://issues.apache.org/jira/browse/EMPIREDB-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz resolved EMPIREDB-377. --- Resolution: Fixed > Page - addFacesMessage always issues WARN-Mess

[jira] [Created] (EMPIREDB-377) Page - addFacesMessage always issues WARN-Message

Jan Glaubitz created EMPIREDB-377: - Summary: Page - addFacesMessage always issues WARN-Message Key: EMPIREDB-377 URL: https://issues.apache.org/jira/browse/EMPIREDB-377 Project: Empire-DB

Re: Lock or rename a remote GIT branch

Hello Rainer, maybe you want to use a tag, not a branch? I guess „renaming“ should work by using just another branch. But I don’t relay know if thats the best solution. Von meinem iPad gesendet > Am 17.02.2022 um 19:37 schrieb Rainer Döbele : > > Hi all, > > does anyone know, whether it

Re: Empire-db version 3.0.0 state of development / Migration of modules

Hello Rainer, sounds and looks interesting! I’d like to try it out with my existing projects. Can you provide a small migration guide / getting started guide? I’m using PostgreSQL and have some postgres-specific functions implemented. I hope I can get them work again ;) - jan > Am

Re: Release time!

branch. > Besides its not that easy as we'd have to find a replacement for the > org.apache.log4j.xml.DOMConfigurator. > > I think the 1.x branch is fine, but I will update the dependency to the > latest 1.7.32. > > Is that OK for you? > > Regards > Rainer > >

Re: Release time!

Hi Rainer at least the jsf2 example uses a very old version of log4j. Maybe that should be updsted? Von meinem iPad gesendet > Am 13.01.2022 um 15:47 schrieb Rainer Döbele : > > Dear empire-db community, > > I hope you have all had a merry Christmas and a happy new year's eve and I > want

Re: [VOTE] Release Apache Empire-db 2.5.0 (rc1)

+1 Von meinem iPad gesendet > Am 04.05.2020 um 18:35 schrieb Rainer Döbele : > > Hi all, > > > > it took a while, but now we have just prepared the apache-empire-db-2.5.0 > release and we are now looking for approval to publish the release. > > More info on release requirements can be

[jira] [Resolved] (EMPIREDB-327) CheckboxInputControl ignores isFieldReadOnly

[ https://issues.apache.org/jira/browse/EMPIREDB-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz resolved EMPIREDB-327. --- Resolution: Fixed > CheckboxInputControl ignores isFieldReadO

[jira] [Created] (EMPIREDB-327) CheckboxInputControl ignores isFieldReadOnly

Jan Glaubitz created EMPIREDB-327: - Summary: CheckboxInputControl ignores isFieldReadOnly Key: EMPIREDB-327 URL: https://issues.apache.org/jira/browse/EMPIREDB-327 Project: Empire-DB Issue

Re: [VOTE] Releasing version 2.5.0

Hi Rainer, I’m using the 2.5 snapshot in production so its an easy +1 from me. But one thing: why not remove all that deprecated stuff and call it 3.0? - jan > Am 14.02.2020 um 10:25 schrieb Rainer Döbele : > > Hello everybody, > > over the last 12 months we have collected many significant

[jira] [Resolved] (EMPIREDB-325) TextInputControl: required-Styleclass is not updated after ajax call

[ https://issues.apache.org/jira/browse/EMPIREDB-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz resolved EMPIREDB-325. --- Resolution: Fixed added in commit d95b26d3d19d12044c9ebdcdecd3f4ca0aaac4b6

[jira] [Created] (EMPIREDB-325) TextInputControl: required-Styleclass is not updated after ajax call

Jan Glaubitz created EMPIREDB-325: - Summary: TextInputControl: required-Styleclass is not updated after ajax call Key: EMPIREDB-325 URL: https://issues.apache.org/jira/browse/EMPIREDB-325 Project

[jira] [Resolved] (EMPIREDB-321) TextInputControl: Improve the ability to implement custom parsing

[ https://issues.apache.org/jira/browse/EMPIREDB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Glaubitz resolved EMPIREDB-321. --- Resolution: Fixed > TextInputControl: Improve the ability to implement custom pars

[jira] [Created] (EMPIREDB-321) TextInputControl: Improve the ability to implement custom parsing

Jan Glaubitz created EMPIREDB-321: - Summary: TextInputControl: Improve the ability to implement custom parsing Key: EMPIREDB-321 URL: https://issues.apache.org/jira/browse/EMPIREDB-321 Project

[jira] [Commented] (EMPIREDB-320) JSF Input skip default JSF input validations

[ https://issues.apache.org/jira/browse/EMPIREDB-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986725#comment-16986725 ] Jan Glaubitz commented on EMPIREDB-320: --- Hi Rainer, I'd like to change number parsing

[jira] [Comment Edited] (EMPIREDB-320) JSF Input skip default JSF input validations

[ https://issues.apache.org/jira/browse/EMPIREDB-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985851#comment-16985851 ] Jan Glaubitz edited comment on EMPIREDB-320 at 12/2/19 8:53 AM: Ok I

[jira] [Comment Edited] (EMPIREDB-320) JSF Input skip default JSF input validations

[ https://issues.apache.org/jira/browse/EMPIREDB-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985851#comment-16985851 ] Jan Glaubitz edited comment on EMPIREDB-320 at 12/2/19 8:10 AM: Edit: I

[jira] [Comment Edited] (EMPIREDB-320) JSF Input skip default JSF input validations

[ https://issues.apache.org/jira/browse/EMPIREDB-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985851#comment-16985851 ] Jan Glaubitz edited comment on EMPIREDB-320 at 12/2/19 6:23 AM: Hi

[jira] [Comment Edited] (EMPIREDB-320) JSF Input skip default JSF input validations

[ https://issues.apache.org/jira/browse/EMPIREDB-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985851#comment-16985851 ] Jan Glaubitz edited comment on EMPIREDB-320 at 12/2/19 6:23 AM: Hi

[jira] [Comment Edited] (EMPIREDB-320) JSF Input skip default JSF input validations

[ https://issues.apache.org/jira/browse/EMPIREDB-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985851#comment-16985851 ] Jan Glaubitz edited comment on EMPIREDB-320 at 12/2/19 6:22 AM: Hi

[jira] [Commented] (EMPIREDB-320) JSF Input skip default JSF input validations

[ https://issues.apache.org/jira/browse/EMPIREDB-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985851#comment-16985851 ] Jan Glaubitz commented on EMPIREDB-320: --- Hi Rainer, thanks for the changes, but now its even

[jira] [Commented] (EMPIREDB-320) JSF Input skip default JSF input validations

[ https://issues.apache.org/jira/browse/EMPIREDB-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985039#comment-16985039 ] Jan Glaubitz commented on EMPIREDB-320: --- Hi Rainer, it looks like this breaks decimal input

[jira] [Commented] (EMPIREDB-315) Extends Options allowing Entries to be active/inactive

[ https://issues.apache.org/jira/browse/EMPIREDB-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16963966#comment-16963966 ] Jan Glaubitz commented on EMPIREDB-315: --- Hi Rainer the last commit

[jira] [Commented] (EMPIREDB-307) Allow overrides of TagEncodingHelper class

[ https://issues.apache.org/jira/browse/EMPIREDB-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952668#comment-16952668 ] Jan Glaubitz commented on EMPIREDB-307: --- Hi Rainer, why have it into the datatable? I have

[jira] [Commented] (EMPIREDB-307) Allow overrides of TagEncodingHelper class

[ https://issues.apache.org/jira/browse/EMPIREDB-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952604#comment-16952604 ] Jan Glaubitz commented on EMPIREDB-307: --- Hi Rainer, Sorry - I missed something in my description

[jira] [Commented] (EMPIREDB-307) Allow overrides of TagEncodingHelper class

[ https://issues.apache.org/jira/browse/EMPIREDB-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952548#comment-16952548 ] Jan Glaubitz commented on EMPIREDB-307: --- Hi Rainer, I think this introduced a bug. - I have

[jira] [Created] (EMPIREDB-308) WebApplication: Add "destroy"-method

Jan Glaubitz created EMPIREDB-308: - Summary: WebApplication: Add "destroy"-method Key: EMPIREDB-308 URL: https://issues.apache.org/jira/browse/EMPIREDB-308 Project: Empire-DB

Re: Report time / Plans for 2018

Hi Rainer, I think the 2.4.7 is currently in good shape. We could think about EMPIREDB-195 for that release. I added a comment to that ticket a few weeks ago. - jan > Am 11.02.2018 um 12:16 schrieb Rainer Döbele : > > Dear fellow comitters, > > its report time again for

DBDatabase.SYSDATE vs. getSystemDateExpr()

Hi all, I just noticed that there is a difference between using DBDatebase.SYSDATE and the method getSystemDateExpr(). DBDatabase.SYSDATE results in CURRENT_DATE (eg 2018-01-15), but getSystemDateExpr() results in NOW() (eg 2018-01-15 09:22:05.063118+01). Is this on purpose or a Bug? - jan

Re: Merry Christmas and future plans

uld be willing to have a look at it and possibly complete it. > > Regards, > Rainer > > >> from: Jan Glaubitz [mailto:j...@glaubitz.org] >> to: dev <dev@empire-db.apache.org> >> subject: Re: Merry Christmas and future plans >> >> Hi Rainer

Re: Re-usable DBCommand with DBClobData

Hello Rainer, EMPIREDB-261 is created. - jan Von meinem iPhone gesendet > Am 12.07.2017 um 12:58 schrieb Rainer Döbele : > > Hi Jan, > > yes, this is a bug. > > What is missing IMO is calling reset() in the getter of DBClobData.getReader() > e.g. like this: > >/** >

Re: [VOTE] Release Apache Empire-db 2.4.6 (rc2)

Hello Rainer, SHA works now (but: maybe we should use at least SHA256?) I'm still unable to verify the PGP signature. - jan Von meinem iPhone gesendet > Am 10.01.2017 um 08:18 schrieb Rainer Döbele : > > Hi Jan, > > you are absolutely right: instead of the sha hash the

Re: New release once again

, > > so which issues have been fixed and how do we get them on the master? > > Rainer > >> From: Jan Glaubitz [mailto:j...@glaubitz.org] >> To: dev <dev@empire-db.apache.org> >> Cc: priv...@empire-db.apache.org >> Subject: Re: New release once again >&

Re: New release once again

Hi Rainer, IMO we should release 2.4.6, it contains a few fixes for MySQL. EMPIRE-247 is still not ready and still unknown if we should do it at all. - jan > Am 03.01.2017 um 14:58 schrieb Rainer Döbele : > > Dear fellow committers, > > first, I want to wish you all a very

Re: Release time?

Hello Rainer, > Can anyone please check, if the following issues can be closed: > > EMPIREDB-247 Add Support for "insertOrUpdate" ("UPSERT") Its not complete, but its in its own branch. So its safe to make a release without it. - jan Von meinem iPhone gesendet > Am 29.10.2016 um 18:39

Re: Build failed in Jenkins: Empire-db snapshot #812

Sorry, should be fixed now. I'll listen to http://shamenun.com/ for a while... - jan Von meinem iPhone gesendet > Am 13.10.2015 um 08:59 schrieb Francis De Brabandere : > > Hi Jan, > > Can you please have a look at this. There are compilation errors in >