I'm cleaning up xml in some tafs, and I'm again struck by the way the
Studio leaves poop in the <DataDictionary> stanza. Basically, every
column that the Studio has ever seen in search/update/delete/insert
actions is kept forever. So when you port databases, you're left
with legacy column definitions in the taf, leading larger and larger
files, which must impact performance. That's one reason I've been
moving all my actions (except Updates/Inserts with BLOBs greater than
32k) to DirectDBMS.
But it occurs to me that this Studio sloppiness is probably related
to the !CST issue. I bet when the Studio can't resolve old column
types, all of the duplicates get changed to !CST.
Maybe a DataDictionary cleaner is needed?
Bill
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
