Golden Code Redmine

03/04/2025

02:07 AM Database Feature #7020: always use "expanded" extent fields

*7020c* was rebased to trunk *15752* and is now at revision *15777*. Last 5 revisions have some performance improveme... Stefanel Pezamosca

02/28/2025

05:57 AM Database Feature #7020: always use "expanded" extent fields

*7020c* was rebased to trunk *15747* and is now at revision *15771*. Stefanel Pezamosca

02/21/2025

08:55 AM Database Feature #7020: always use "expanded" extent fields

*7020c* was rebased to trunk *15724* and is now at revision *15748*. Stefanel Pezamosca

02/18/2025

08:04 AM Database Feature #7020: always use "expanded" extent fields

First try to solve contains for expanded extent fields in a temp-table looks like this:
For example, for a field n... Stefanel Pezamosca

02/14/2025

02:09 AM Database Feature #7020: always use "expanded" extent fields

The *7020c* rebased with *trunk* revision *15703*. New revision is *15723*. Stefanel Pezamosca

02/13/2025

09:48 AM Database Feature #7020: always use "expanded" extent fields

I did some other small changes and *7020c* is now at revision *15707*.
With denorm-extent the name of the word tab... Stefanel Pezamosca

02/07/2025

04:19 AM Database Feature #7020 (Review): always use "expanded" extent fields

7020c was rebase to trunk revision 15687.
I have committed 15704/15705, please review:
Removed support for denorm... Stefanel Pezamosca

02/05/2025

09:25 AM Database Feature #7020 (WIP): always use "expanded" extent fields

I started removing some denormalized / custom-extent references and seems to work well.
But, there is an issue I for... Stefanel Pezamosca

04:09 AM Database Feature #7020: always use "expanded" extent fields

So, should I remove all references to @denormalized@ / @custom-extents@ and keep just the @normalized@ and @expanded@... Stefanel Pezamosca