: Wednesday, October 19, 2005 8:18 PM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: OS X.4
Dang! Found 48 occurences in 5 files. But there not everywhere.
I'll
have to grep my production server and see how many are there, vs. how
many are from the last month of significant cutting
20, 2005 2:06 PM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: OS X.4 - Danger in correcting... (solved)
Steve,
lets check something.
make a backup copy of your file, and change your values to:
Column DataType=!CST ColumnType=0
TableNameProducts/TableName
ColumnName![CDATA
We're using Tiger 10.4.2 and Oracle via JDBC, and have never
experienced insert or update action corruptions. Could this be
database and/or DB connector related?
We do occasionally see a tcf object's scope get lost shortly after
being added to a TAF, but after it gets changed once (or
I have seen it with primebase, and MSSQL 2000, and MYSQL.
--
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/ -
I checked my files for the !CST characters and sure enough, I DID
find them throughout recently edited TAFs and TCFs. We haven't seen
much instability in our production instance that could be related to
inserts and updates, but perhaps this was because we are not using
the Witango server,
to this
issue.
-Original Message-
From: Robert Garcia [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 20, 2005 6:44 AM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: OS X.4
I have seen it with primebase, and MSSQL 2000, and MYSQL.
--
Robert Garcia
President - BigHead
to be safe, create another taf with a search action that pulls from the same table. It will create a "good" data dictionary in the new taf. Using a text editor, copy it and paste it wherever the 'bad' taf has the corresponding corrupt data dictionary section. On Oct 19, 2005, at 4:55 PM,
-9205
[E-mail] [EMAIL PROTECTED] or [EMAIL PROTECTED]
-Original Message-
From: Bill Conlon [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 19, 2005 8:18 PM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: OS X.4
Dang! Found 48 occurences in 5 files. But there not everywhere
0-499-9200
[Fax]610-499-9205
[E-mail] [EMAIL PROTECTED] or [EMAIL PROTECTED]
-Original Message-
From: Bill Conlon [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 19, 2005 8:18 PM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: OS X.4
Dang! Found 48 occurences
After editing the TAFs / TCFs (with a text editor, BBEdit), I found
that some tafs now had a corrupted structure as reported by the
Witango server. If I just created a new TAF and dragged over the
actions from the old one, the TAFs ran correctly. But when I examined
the XML for the
and manually replacing them.
Peter
- Original Message -
From: Dale Graham [EMAIL PROTECTED]
To: witango-talk@witango.com
Sent: Thursday, October 20, 2005 4:58 PM
Subject: Re: Witango-Talk: OS X.4 - Danger in correcting...
After editing the TAFs / TCFs (with a text editor, BBEdit), I
This seems to me to be a sound practice prior to deploying
applications. I'll plan on it.
So I guess the answer to my original question is that I might as well
install X.4, and follow Peter's recommendation.
thx,
bill
On Thursday, October 20, 2005, at 09:10 AM, Peter Ternstrom wrote:
@witango.com
Subject: Re: Witango-Talk: OS X.4
Dang! Found 48 occurences in 5 files. But there not everywhere.
I'll
have to grep my production server and see how many are there, vs. how
many are from the last month of significant cutting and nailing.
Is there some rhyme or reason. If I replace
it shouldn't show corrrupt, if you JUST change !CST to the right
datatype, like vcha or tims. I have done this MANY times. maybe you
changed something else also?
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
: Witango-Talk: OS X.4 - Danger in correcting...
After editing the TAFs / TCFs (with a text editor, BBEdit), I
found that some tafs now had a corrupted structure as reported
by the Witango server. If I just created a new TAF and dragged
over the actions from the old one, the TAFs ran correctly
, but it sure beats
using a text editor and manually replacing them.
Peter
- Original Message -
From: Dale Graham [EMAIL PROTECTED]
To: witango-talk@witango.com
Sent: Thursday, October 20, 2005 4:58 PM
Subject: Re: Witango-Talk: OS X.4 - Danger in correcting...
After editing the TAFs
]]/ColumnName
/Column
-Original Message-
From: Peter Ternstrom [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 20, 2005 11:10 AM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: OS X.4 - Danger in correcting... (solved)
Hello All,
i have also seen the !CST in my tafs for a while now (Win 5.5
in.
Im not 100% sure on this, so I really hope we could get some input from
witango on this.
Peter
- Original Message -
From: Fogelson, Steve [EMAIL PROTECTED]
To: witango-talk@witango.com
Sent: Thursday, October 20, 2005 6:53 PM
Subject: RE: Witango-Talk: OS X.4 - Danger
]]/ColumnName
/Column
Column DataType=long ColumnType=0
TableNameProducts/TableName
ColumnNameP_ID/ColumnName
/Column
-Original Message-
From: Peter Ternstrom [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 20, 2005 1:52 PM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: OS X.4
: Thursday, October 20, 2005 9:01 PM
Subject: RE: Witango-Talk: OS X.4 - Danger in correcting... (solved)
Peter,
I checked again and the table node is complete for fields following the
fields with the CST DataType. Kinda looks like it is correct, but heck
if I know.
Thanks
Steve
Column DataType=!CST
Fogelson, Steve at [EMAIL PROTECTED] wrote:
ColumnName![CDATA[Products.P_Oversize as FType]]/ColumnName
If I open an old T2000 TAF with fields that have spaces in the name in WT5
Editor it corrupts them as above. T2000 supported spaces in filed names, WT5
doesn't.
Wayne
Byte
I do, and there are others, like Mark Weiss and Roland.
There is a serious bug that I don't think is JUST 10.4, but seems to
show up more in 10.4. Your insert and update actions can get
corrupted. It is a major pain, it has been reported to Witango months
ago. It has not been acknowledged,
Thx much. I found a used dual G4 1.25 GHz for the price of a mini, so
I'll probably stick with X.3.9.
BTW, I've never had the corruption issue while running X.2.8.
bill
On Wednesday, October 19, 2005, at 03:00 PM, Robert Garcia wrote:
I do, and there are others, like Mark Weiss and
search your tafs fors !CST with a text editor.
see if you have any. I had some, with no error, and didn't realize
it, then I started seeing the errors later.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph:
sorry, that is, search for !CST.
--
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 Oct 19,
egads!!!
I just searched for !CST and it is all over the place in my tafs (and
my server has been VERY unstable recently so this may be contributing to
the delinquency of a server)... question, what should I do? Okay to
delete all the Data Dictionary sections with this datatype, or do I
Dang! Found 48 occurences in 5 files. But there not everywhere. I'll
have to grep my production server and see how many are there, vs. how
many are from the last month of significant cutting and nailing.
Is there some rhyme or reason. If I replace INSERT/UPDATE with
DirectDBMS does
Well I have WAY more than 48 instances... my search returned 1420
instances in 46 files... and as I said earlier, my servers have been
bouncing like a yo-yo recently... fatal exceptions, generally associated
with a DB call... so I'm really suspicious that this could be involved...
again...
sometimes, you can rebuild the action in the taf, and it will fix.
SOMETIMES.
But the best thing to do, is too go in, and change the !CST to the
correct datatype with a text editor.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park
I also see this issue. But only in Search criteria. The comparator drop down
will show numeric type comparisons for text fields. So it only gives options
like '=' or '' when what a really want is 'contains'.
I assumed it was not getting the correct data type from the datasource (in
this case
I have a program I wrote, that is not ready to give out, but if you
tell it the odbc data source, will fix em. But I don't think I should
be spending the time an money to fix this for all, and I would like
to at least get an acknowledgement. Witango may already know of a
workaround, have a
31 matches
Mail list logo
