This content has been marked as final. Show 4 replies
In your example, you need to create a new table, say MYAPP_USER, and define it as an auxiliary table in the user item descriptor.
So, your extended userprofile.xml looks something like this.
<item-descriptor name="user" cache-mode="disabled">You can use the auxiliary tables to hold additional info.
<table name="MYAPP_USER" type="auxiliary" id-column-name="user_id">
<property name="myProperty" display-name-resource="Custom Properties" column-name="MY_NEW_COLUMN" data-type="string" />
Hope this helps.
Keep posting the updates / questions.
Could you please more specific about the use of Auxilary Table.Such table have one to one relationship with primary table in item-descriptor. See below:
Multi tables having one to many relationship with primary table in item-descriptor.
can i make here my table dps_user type as auxilary in itemdescriptor user.You should not override primary table. To add new column see Gopinath's post and below thread for complete format of xml file:
Adding a new column to an existing database table
ATG provides a primary table for each item descriptor shipped with the product.
In future ATG versions, the definition of the fields in those default tables might change, so it is considered a bad practice from the upgradeability point of view to modify those.
Instead, ATG provides the auxiliary table mechanism so you can add as many new fields as you might need. They will have a 1 to 1 relationship to the primary table, and as long as you configure your repository correctly, from ATG point's of view there is no difference in whether you defined your properties in the primary or the auxiliary table.
Hope that helps.