Activity

From 05/05/2015 to 06/03/2015

10:43 PM Bug #2552: bad hql caching prevents queries to position on the correct rows: Ovidiu, was your 0603a update meant to be applied on top of the 0421a update?
I tested P2J 10871 + 0603a (without ... Eric Faulhaber

02:47 PM Bug #2552: bad hql caching prevents queries to position on the correct rows: > Looks good, nice find. Agreed, will look better with the println statements removed. Do you want to leave these beh... Ovidiu Maxiniuc
02:33 PM Bug #2552: bad hql caching prevents queries to position on the correct rows: Code review 0603a:
Looks good, nice find. Agreed, will look better with the println statements removed. Do you wan... Eric Faulhaber
02:07 PM Bug #2552: bad hql caching prevents queries to position on the correct rows: Eric,
I found the probable cause for the failures in regression testing of the @?@ relational semantics. I was worki... Ovidiu Maxiniuc

01:25 PM Feature #2580: make field denormalization the default schema conversion for extent fields: For a schema with a lot of tables requiring extent field denormalization, it would be simpler and less error prone to... Eric Faulhaber
01:21 PM Feature #2580 (New): make field denormalization the default schema conversion for extent fields: Eric Faulhaber

12:42 PM Bug #2536: improve dynamic query parser error handling: Code review 0519a:
I'm glad you made this change, I was going to ask for something like it. After you made the err... Eric Faulhaber

03:37 AM Bug #2536: improve dynamic query parser error handling: I added a few changes to @DynamicQueryHelper@ that refine the messages printed in console. At this moment the log is ... Ovidiu Maxiniuc

03:53 PM Bug #2536: improve dynamic query parser error handling: Is there anything left to do on this issue at this point, or can it be closed? Eric Faulhaber
03:51 PM Bug #2577: extent information in meta table: Ovidiu Maxiniuc wrote:
> I've just checked the @custom-extent@ support. As you thought, it doesn't work. The @messag... Eric Faulhaber
03:16 PM Bug #2577: extent information in meta table: Committed to bzr as revno 10865.
I've just checked the @custom-extent@ support. As you thought, it doesn't work. T... Ovidiu Maxiniuc
02:10 PM Bug #2577: extent information in meta table: Code review 0518b:
The fix looks fine. Please check it in as is, no regression testing needed (it is additive and ... Eric Faulhaber
12:54 PM Bug #2577: extent information in meta table: I discovered that the extent information is missing in the field meta table (it's always @0@). This causes some testc... Ovidiu Maxiniuc
12:38 PM Bug #2577 (Closed): extent information in meta table: Ovidiu Maxiniuc

01:53 PM Bug #2488: replace runtime compilation of dynamic queries: Eric Faulhaber wrote:
> Code review 0512a:
>
> The change looks good. If it fixes your problem locally, please co... Ovidiu Maxiniuc
12:37 PM Bug #2488: replace runtime compilation of dynamic queries: Code review 0512a:
The change looks good. If it fixes your problem locally, please commit and distribute, since re... Eric Faulhaber
11:47 AM Bug #2488: replace runtime compilation of dynamic queries: The attached update allows variables to be declared and initialized in the dynamically constructed object. They were ... Ovidiu Maxiniuc

12:53 PM Bug #2570 (Closed): buffers must be members of the class which defines their tightest scope: The attached fix resolves the original problem and the items in notes 6-8. It has passed regression testing and is co... Eric Faulhaber

03:18 AM Bug #2570: buffers must be members of the class which defines their tightest scope: The third item in note 6 was actually a more serious latent bug than I thought. Buffer name conflict resolution was g... Eric Faulhaber

01:25 PM Bug #2570: buffers must be members of the class which defines their tightest scope: > With my update, it doesn't compile.
Congrats! You made it more correct. :) Greg Shah
01:22 PM Bug #2570: buffers must be members of the class which defines their tightest scope: The types of failures I'm seeing:
* A buffer which previously was a top-level instance variable is referenced in a... Eric Faulhaber
12:31 PM Bug #2570: buffers must be members of the class which defines their tightest scope: Greg Shah wrote:
> Code Review ecf_upd20150506a.zip
>
> I don't see much in the way of problems. Where there man... Eric Faulhaber
10:04 AM Bug #2570: buffers must be members of the class which defines their tightest scope: Code Review ecf_upd20150506a.zip
I don't see much in the way of problems. Where there many changes to the MAJIC c... Greg Shah
03:58 AM Bug #2570: buffers must be members of the class which defines their tightest scope: I've decided to defer the name conflict improvements indefinitely, as it turns out there's a lot of potential breakag... Eric Faulhaber

04:17 PM Bug #2570: buffers must be members of the class which defines their tightest scope: There were regressions with naming conflicts. Working on a fix. Eric Faulhaber
12:10 PM Bug #2570: buffers must be members of the class which defines their tightest scope: P2J incorrectly creates all record buffers as instance members of the top level class. Buffers scoped more tightly th... Eric Faulhaber
11:46 AM Bug #2570 (Closed): buffers must be members of the class which defines their tightest scope: Eric Faulhaber

Also available in: Atom

FWD » Core Development » Database