---
** [tickets:#895] imm: Allow class schema change to add attribute default **
**Status:** unassigned
**Milestone:** future
**Created:** Fri May 09, 2014 01:32 PM UTC by Anders Bjornerstedt
**Last Updated:** Fri May 09, 2014 01:32 PM UTC
**Owner:** nobody
Currently it is not allowed to add a default value to an attribute definition
that has no prior default. Only changes to an existing default are allowed.
This enhancement will remove this restriction, allowing a class schema change to
add a default to an attribute definition.
Only new instances of that class will get the default assigned when no value is
provided for the attribute at object-create time.
Old instances with a null-value for that attribute will still have a null-value
for that attribute even after the schema change. A general rule for schema
changes is that the immsv never alters the value of existing attributes as
part of a schema change. Doing so would require the OI to be notified, which is
not realistic since the shcema change is not performed as a CCB.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
