I even started an to do that. but it requires a lot of user input,
cuz it needs to login to the odbc dsn, to look at datatypes, and the
dsn info in the tafs are encrypted, user/password.
I abandoned it, since witango inc finally admitted the bug, and said
they were planning a release of beta of v6 studio, or 5.3/4 by the
end of march. With my luck, I would do all the work, and it would
come out the next day.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On May 12, 2006, at 10:31 AM, William M Conlon wrote:
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
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
