Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
15 replies
Subscribers
7 subscribers
Views
4977 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Hi All, Here is my situation for writing xsd's had 3 c
saratrk
over 11 years ago
Hi All,
Here is my situation for writing xsd's
had 3 cdt's
1. client - xsd created - table created
2. employee - xsd created - table created
3. pay
in this pay cdt PK of client and PK of employee are the foreign keys and they are mapped with "many to one" relationship with those 2 (means many records in pay can have single client or employee )
I already have referred
forum.appian.com/.../Defining_a_Custom_Data_Type
and written xsd for pay with following annotations.
<?xml version="1.0" encoding="utf-8" ?>
<xsd:schema xmlns="urn:appian:example:assocations:many-to-one" elementFormDefault="qualified" targetNamespace="urn:appian:example:assocations:many-to-one" xmlns:xsd="
www.w3.org/.../XMLSchema">
<xsd:complexType name="pay">
--
<xsd:element minOccurs="0" nillable="false" maxOccurs="unbounded" name="clientId" type="client">
<xsd:annotation>
<xsd:appinfo source="appian.jpa">
@ManyToOne
...
OriginalPostID-77431
OriginalPostID-77431
Discussion posts and replies are publicly visible
Parents
0
Sathya Srinivasan
Appian Employee
over 11 years ago
Sarat, I haven't tried your relationship but in general, I tend to keep the reverse relation to a minimum in my data model. Instead of a many to one association within the CDT, you may want to consider holding the PK in the related table. This will allow you to query the data on demand rather than loading the entire data all the time which may or may not be necessary.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Sathya Srinivasan
Appian Employee
over 11 years ago
Sarat, I haven't tried your relationship but in general, I tend to keep the reverse relation to a minimum in my data model. Instead of a many to one association within the CDT, you may want to consider holding the PK in the related table. This will allow you to query the data on demand rather than loading the entire data all the time which may or may not be necessary.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data