on 05-08-2006 3:19 PM
It looks like the Java Dictionary features are quite limited. From what I've read I understand this is because of being portable between databases.
But I wonder how you then implement i.e. database views. Only define the logical structures in the Dynpro project, and leave the view-related logic to the data layer classes?
And what about auto-generated columns (SqlServer identity or Oracle Sequences)? The same philosophy? Not bother about it in the presentation and business layer?
I have browsed through all tutorials to find an example of such a program, but I can not find it...
Hi Raj,
Do you have some specifis on what you require to for your persistency...
Perhaps,then details would help solve any issues you face...
Regards,
Vidya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jan,
We are evaluating using the Dictionary Component for our persistence.
Can you tell us your experience with Dictionary and/or using custom datasources?
Thanks
Raj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.