class initialization with default values

[disaster]

as per http://qcu.be/content/default-values-db-definition#comment-2567 it would be nice to be able to configure if the classes fields have to be initialized with default values form database, so we always save a valid object (otherwise we could have not set some not-null values)

[VexedPanda]

Probably best to offload it to a subtemplate, for readability and customization purposes.

Also, to maintain the current performance for apps that don't need this, maybe we should move the construct call as part of the non-base file, and have it commented out, similar to the way there are SAMPLE LOAD METHODS..?

That should make it dead simple for anyone that wants to use it to do so, while not impacting performance of existing apps, or apps that don't need to use defaults.

[disaster]

Ok, I have tried to make it a subtemplate, but I couldnt make it..I'll try again :-)

[MikeHostetler]

I agree with VexedPanda?, this is an awesome patch! Thanks disaster!

[VexedPanda]

I love it. If you've actually generated with this, and it initializes correctly once you uncomment the constructor, let's commit it. :)

[disaster]

It still has some problems: for example on my postgresql database a "serial" filed has this default value:

/**
 * Protected member variable that maps to the database PK Identity column user.id
 * @var integer intId
 */
protected $intId;
const IdDefault = 'nextval(\'user_id_seq\'::regclass)';

which creates some problems :-)

what shall I do?

[disaster]

don't put meaningless default values for serial fields

[disaster]

too many tabs

[VexedPanda]

Good catches. So with these changes, everything is working great then? :)

[disaster]

In my setup, yes.
Another nice way of using this is to initialize the class in the meta_control, so if we have, for example a field "active" boolean, and default to true, it will be checked automatically on.
I have a patch also for this, disabled by default :-)

[disaster]

add default initialization to meta control (disabled by default)

[VexedPanda]

Interesting. If we uncomment the constructor in the first patch, that acheives the same effect for the meta control, does it not?

It hadn't occurred to me that a dev would want the GUI control initialized, but not progamatically created ones, but I like it. :)

[disaster]

Yes, I think that the best way of using it is to call Inizialize after you create the metacontrol on an editpanel :-) (so you have valid values also for controls that are hidden but NOT NULL)

[VexedPanda]

Tests out ok so far, and the code looks clean. I'll commit. :)

[VexedPanda]

(In [506]) Fixes #317 provides option for object or metacontrol initialization based on default values.

[disaster]

great!