J
Jiho Han
Can someone explain these two?
I read the description on the SDK doc and some explanations on the web but
just can't seem to get my head wrapped around the concept. Is it that SchemaType.Source
will ignore TableMappings altogether and create tables and columns as is
in the database? So if there were already tables and columns in the dataset
that has identical names, would the adapter throw an exception or ignore
it? And if I use SchemaType.Mapped, is the adapter ignoring the schema (tables
and columns) that do not appear in the TableMappings completely? Wait, if
that's the case, what's the point of using SchemaType.Mapped in the first
place? Is this enumeration just about table and column names? So then,
it's really for retrieving constraints info, correct? such as nullability,
primary key, etc.
Sorry about rambling on.
Thanks in advance.
Jiho Han
Senior Software Engineer
Infinity Info Systems
The Sales Technology Experts
Tel: 212.563.4400 x216
Fax: 212.760.0540
(e-mail address removed)
www.infinityinfo.co
I read the description on the SDK doc and some explanations on the web but
just can't seem to get my head wrapped around the concept. Is it that SchemaType.Source
will ignore TableMappings altogether and create tables and columns as is
in the database? So if there were already tables and columns in the dataset
that has identical names, would the adapter throw an exception or ignore
it? And if I use SchemaType.Mapped, is the adapter ignoring the schema (tables
and columns) that do not appear in the TableMappings completely? Wait, if
that's the case, what's the point of using SchemaType.Mapped in the first
place? Is this enumeration just about table and column names? So then,
it's really for retrieving constraints info, correct? such as nullability,
primary key, etc.
Sorry about rambling on.
Thanks in advance.
Jiho Han
Senior Software Engineer
Infinity Info Systems
The Sales Technology Experts
Tel: 212.563.4400 x216
Fax: 212.760.0540
(e-mail address removed)
www.infinityinfo.co