Activity
From 08/19/2020 to 09/17/2020
09/17/2020
- 04:52 PM Feature #4011: database/persistence layer performance improvements
- Roger Borrello wrote:
> Is this a safe setting to add into existing projects? In other words, is there a downside ... - 04:38 PM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> It is *disabled* by default (meaning normal 4GL behavior: temp-tables are undoable unless de... - 03:58 PM Feature #4011: database/persistence layer performance improvements
- The performance enhancement to force NO-UNDO mode for all temp-tables (regardless of how they were defined) is implem...
- 02:50 PM Support #4701: try to improve H2 transaction commit performance
- Adrian: Go ahead and merge into 3821c. If there are any special requirements for rebuilding/deployment, please notif...
- 01:36 PM Support #4701: try to improve H2 transaction commit performance
- Adrian, thanks for the explanations. Greg, I am good with the update going into 3821c.
09/16/2020
- 05:16 AM Support #4701: try to improve H2 transaction commit performance
- Just rebased 4701a using 3821c.
- 03:36 AM Support #4701: try to improve H2 transaction commit performance
- Eric Faulhaber wrote:
> Code review 4701a, rev 11624-11627:
>
> This review is for the private vs. shared temp-ta...
09/15/2020
- 07:24 PM Support #4701: try to improve H2 transaction commit performance
- Code review 4701a, rev 11624-11627:
This review is for the private vs. shared temp-table database implementation. ...
09/14/2020
- 05:53 AM Support #4701: try to improve H2 transaction commit performance
- 4701a is independent upon the H2 version.
- 05:51 AM Support #4701: try to improve H2 transaction commit performance
- Does this depend upon a new version of H2?
- 05:07 AM Support #4701: try to improve H2 transaction commit performance
- I find 4701a safe enough. The major change is the new private vs shared temporary database. Using a shared temporary ...
09/13/2020
- 11:13 AM Support #4701: try to improve H2 transaction commit performance
- How risky is 4701a?
09/10/2020
- 05:58 AM Feature #3574: finish implementation of temp-table XML support
- Conversion and runtime stubs for @SERIALIZE-ROW()@ method are in 3821c rev 11512
09/09/2020
- 09:37 AM Feature #4011: database/persistence layer performance improvements
- We don't want to move to 4.1 before we release 4.0. On the other hand, this is a very major change. Until 4.0 is re...
- 09:17 AM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> 4011e was merged to trunk and committed as revision 11348.
Was there a FWD revision numbe... - 04:42 AM Support #4701 (Review): try to improve H2 transaction commit performance
- This task in finished. Waiting to rebase 4701b and eventually merge to trunk/3821c. However, I suggest to keep #4843 ...
09/08/2020
- 06:23 PM Feature #4011: database/persistence layer performance improvements
- Trunk revisions 11347.1.316 and 11347.1.318 implemented a mechanism to keep track of the versions of persistent DMOs ...
- 06:16 PM Feature #4011: database/persistence layer performance improvements
- 4011e was merged to trunk and committed as revision 11348.
- 05:14 PM Feature #2156 (Closed): datetime-tz and hibernate
- Please make the change in 3821c. I'm going to close this task.
> I say probably because the new ORM has not yet b... - 05:11 PM Feature #2156: datetime-tz and hibernate
- Greg Shah wrote:
> @datetime-tz@ field persistence is fully supported now?
Yes, that was one of the aspects we bene... - 04:56 PM Feature #2156: datetime-tz and hibernate
- @datetime-tz@ field persistence is fully supported now? Do we need to change anything in our gap marking?
- 04:48 PM Feature #2156: datetime-tz and hibernate
- Yes.
It is rather obsolete as we have now a much simpler access to DTZ fields using the new ORM. - 04:44 PM Feature #2156: datetime-tz and hibernate
- 4011e was merged to trunk as rev 11348.
Eric/Ovidiu: Can we close this task? - 03:35 PM Support #4701: try to improve H2 transaction commit performance
- Is there anything more to work on in this task or do we just need to get it rebased for merge to trunk (or merge into...
08/21/2020
- 03:07 AM Feature #3814: more schema metadata
- Greg Shah wrote:
> Good job. I think we should pause the work there. Is it safe to include in the branch pending t... - 09:03 PM Feature #3814: more schema metadata
- Good job. I think we should pause the work there. Is it safe to include in the branch pending the final changes?
08/20/2020
- 05:42 PM Feature #3814: more schema metadata
- @UserTableStatUpdater@ core functionality implemented. The exposed public methods are:
* getTableStats(integer con...
Also available in: Atom