Project

General

Profile

Bug #5867

« Previous | 40 of 342 | Next »

today and now initial values are not handled correctly in DmoMeta.existingFields map

Added by Eric Faulhaber over 2 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version:

History

#1 Updated by Eric Faulhaber over 2 years ago

In 3821c/13236, I modified DmoMeta to store a map of P2JFields (by property name), for use in defining dynamic temp-tables. This previously was being handled in code in TempTableBuilder and TableMapper, but the initial field values were not being handled correctly, when the source table from which a dynamic temp-table was derived was itself a temp-table.

One part of the support for initial values I overlooked, however, was that of "dynamic" initial values, such as today or now for date* types. Since the 13236 update was additive and that support wasn't there previously, I will not roll back that revision, but this issue is being created to document this missing aspect of the support.

My initial thought on the implementation is that the P2JField.initial instance variable needs to be a lambda expression returning a BDT, rather than a BDT itself.

Also available in: Atom PDF