That does prevent, MOST of the time, but not all the time,
unfortunately.
--
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 30, 2006, at 2:01 PM, Roland Dumas wrote:
I found that the bug is introduced when one edits an action and
hasn't "opened" or logged into the database from the editor. (hit
the triangle next to the datasource) I actually had one the other
day that cured itself when I found the bug. I opened the database,
then re-opened the taf and the bug had disappeared.
That was a lucky reversal of the bug. The way I take them out
otherwise is to create a new taf, create a new action in the taf
that hits the table, and then copy the data dictionary stanza from
there to the buggy taf.
On May 30, 2006, at 1:19 PM, William M Conlon wrote:
Gaak! (as Bill the Cat used ot squawk). I've run into the
dreaded !CST bug, when I needed to replace a DirectDBMS with an
Insert from an old taf(to workaround <@BIND>'s 32kB data limitation).
I'd like to just hand-edit the offending DataTypes in the
DataDictionary stanza. Has anyone already assembled a table
mapping column types to witango DataTypes?
Here's a start
For MySQL
vcha --> VARCHAR, ENUM, ...
lbin --> MEDIUMBLOB, LONGBLOB
text --> CHAR,
long --> INT(10), INT(11)
Bill
_____________________________________________________________________
___
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
