Yes, we get it here too. Here's what we found:
1. It's random. It does not happen for weeks then you get a flurry.
2. It seems to happen most often when clicking in the Snippets tab at the bottom
right of the editor.
3. Greg McElhinney, one of our programmers here found out if you hav
Dear Peter,
I have found that the editor bombs when using [CTRL]+C and [CTRL]+V (cut and paste)
often, especially if I do a [CTRL]+Z to undo some actions first.
I have learned to save my work often, but the problem does get to be annoying after a
while of programming.
Mike
-Original Messa
That makes sense. Thanks for the info!
> -Original Message-
> From: Customer Support [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 01, 2004 5:58 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Witango-Talk: Question about argument names
>
>
> There is no speed improvement by using _functio
I learned this the hard way. Not only was I doing next and previous
buttons, but I had listed pages as well. I removed all the "_" from
"_function" and turned debug on and watched as every click added more
uneeded args to the post. After clicking 20 or 30 pages, the "next"
would would pretty mu
Not to worry, there was no secret ( or further communication off-line with
Witango reps ).
(BTW: The entire thread is available at www.witango.com / Developer
Resources / Mail List Archives )
I solved my original problem using a semaphore (javabeans) as an external
source of synchronization.
-
Why is the first transaction "Read Uncommitted"?
Read uncommitted reads rows that have been changed by
other database users in a transaction, but for which
the transaction has not been committed or rolled back.
Is this what you intended and if you change that first
Begin Transaction to Exclusive
Thank you for your reply.
"Read Uncommitted" was the equivalent of a typo; I accidentally modified
that action while trying to "beautify" the taf (with labels that are easier
to understand then those used in my actual testfile). Sorry for the
confusion.
I can confirm that the deadlock occurs w
Mihai ,
Just to clarify this issue. It is the database that is deadlocking and
not the witango server. The error is being returned from the database.
[Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID
60) was deadlocked on {lock} resources with another process and has
been
Hello,Thank you for your fast
response.I agree this is an error reported by MS-SQL and it is the DB
that is deadlocked; actually I never implied it otherwise. But the
functionality of BT-ET is provided by Witango; and this is the subject of my
message.I agree that my code was not the optimal
Mihai,
I believe that the assumption or request you suggested, that the code
should be optimized inside a transaction so that deadlocks do not
occur, is too strong and risky and in fact it denies the very concept
it tries to implement. It's got to be a way of making sure that a
transactio
Mihai,
I can add some thoughts, which might help
clarify things for you.
First off, everything you are discussing
here is a function of the SQL server. Witango is simply sending the SQL
statements BEGIN TRANS and COMMIT TRANS when you use the BT and ET actions,
respectively.
Wh
11 matches
Mail list logo
