Delay Editor and teamcoding (beta 22)

Toad for Oracle - Beta
1

Hi,

just installed the new beta 22 and logged in to vcs (automaticly login). What I encounter now is that every query I try to run has a delay of about 8 seconds in my case. I spooled the sql to screen and see a SQL query for tcx_objects (just looks like a " select * from tcx_objects"), and in between this query and the query I want to run sits the delay of 8 seconds (I have about 4000 records in tcx_objects).

I think that TOAD is looking if the query is some kind of object creating or adjusting and checks in teamcoding for it, but it looks not efficient.

Thanks

Herald ten Dam

2

Hi,

extra error. If new object creating in TeamCoding, ORA-1400. Cannot insert null into (“TOAD” ,’ TCX_OBJECTS",LAST_CHECKOUT_DBUSER").

Herald

3

I logged the first issue for the developer. I wasn’t able to replicate the second, but will keep trying.

4

Hey Herald,

That was a bug. It’s been fixed for the next beta.

The new version of Team Coding was designed to automatically alter the TCX_OBJECTS table and drop the NOT NULL constraint on that column upon login, if you have permissions to alter that table that is. If you don’t have permission to alter that table, it should fill that column with your database username – regardless of whether it’s needed. The old version (Toad 12.8 and below) filled in that column for both check-ins and check-outs, which was incorrect. However, the current version was pulling the username from an inconsistent place. I’ve updated this for the next beta.

The easiest way to get around this right now is to log in with an account that is part of the TC_ADMIN role, and it should not happen going forward. Or, you can disable or drop the constraint on the following columns in that table manually:

LAST_CHECKIN_DBUSER

LAST_CHECKIN_OSUSER

LAST_CHECKIN_TIMESTAMP

LAST_CHECKOUT_DBUSER

LAST_CHECKOUT_OSUSER

LAST_CHECKOUT_TIMESTAMP

-John

From: herald.ten.dam [mailto:bounce-heraldtendam@toadworld.com]

Sent: Wednesday, February 03, 2016 5:12 AM

To: toadoraclebeta@toadworld.com

Subject: RE: [Toad for Oracle - Beta Discussion Forum] Delay Editor and teamcoding (beta 22)

RE: Delay Editor and teamcoding (beta 22)

Reply by herald.ten.dam

Hi,

extra error. If new object creating in TeamCoding, ORA-1400. Cannot insert null into (“TOAD” ,’ TCX_OBJECTS",LAST_CHECKOUT_DBUSER").

Herald

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - Beta notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag
this post as spam/abuse.

5

Hey Herald,

The “select * from tcx_objects” is simply a refreshing of the local object cache that happens once at the beginning of a Team Coding action (check-in, check-out, etc). It also happens before execution of a script to help prevent modifications to a database object that might be controlled by Team Coding. Previous versions of Team Coding queried the database multiple times throughout each object’s action, which also had a significant hit on performance.

There are still ways we can optimize the performance, though. A couple of quick questions to help me understand your environment:

  1.  Is your database server local to your office or is it located in a remote office?

  2.  If remote, are you connected through VPN?

  3.  Are you using F5 or F9 when running your query?

-John

From: herald.ten.dam [mailto:bounce-heraldtendam@toadworld.com]

Sent: Wednesday, February 03, 2016 4:58 AM

To: toadoraclebeta@toadworld.com

Subject: [Toad for Oracle - Beta Discussion Forum] Delay Editor and teamcoding (beta 22)

Delay Editor and teamcoding (beta 22)

Thread created by herald.ten.dam

Hi,

just installed the new beta 22 and logged in to vcs (automaticly login). What I encounter now is that every query I try to run has a delay of about 8 seconds in my case. I spooled the sql to screen and see a SQL query for tcx_objects (just looks like a " select * from tcx_objects"), and in between this query and the query I want to run sits the delay of 8 seconds (I have about 4000 records in tcx_objects).

I think that TOAD is looking if the query is some kind of object creating or adjusting and checks in teamcoding for it, but it looks not efficient.

Thanks

Herald ten Dam

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - Beta notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag
this post as spam/abuse.

6

Hi John,

1/2) database server is local to me (maybe 50 meters away :wink: )

  1. Both take the same time. I spooled the sql, so between the CTX_OBJECTS query and the next statement, dbms_output_enable sits 8 seconds. The CTX_OBJECTS query costs only around 0.2 seconds, so something is working in between.

If I take a schema which is not under TC control, the delay is the same.

Herald

7

I’ve made some changes to the logic that should significantly reduce that delay. It should be available in the next beta.

From: herald.ten.dam [mailto:bounce-heraldtendam@toadworld.com]

Sent: Thursday, February 04, 2016 4:18 AM

To: toadoraclebeta@toadworld.com

Subject: RE: [Toad for Oracle - Beta Discussion Forum] Delay Editor and teamcoding (beta 22)

RE: Delay Editor and teamcoding (beta 22)

Reply by herald.ten.dam

Hi John,

1/2) database server is local to me (maybe 50 meters away :wink: )

  1. Both take the same time. I spooled the sql, so between the CTX_OBJECTS query and the next statement, dbms_output_enable sits 8 seconds. The CTX_OBJECTS query costs only around 0.2 seconds, so something is working in between.

If I take a schema which is not under TC control, the delay is the same.

Herald

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - Beta notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag
this post as spam/abuse.

8

John,

I downloaded latest now and will test again, but the problem I had in the 22 version and also in this new version is that TOAD when it starts up and connect to a schema which is under TeamCoding, he checks in git for the user the number of objects. I have 4000 objects under control in git, every time he issues an " git.ext config user.name" and this cost about 0.1 second. So I have to wait about 5 min before TOAD gives me some respond. On other occasions I see TOAD keeps checking for the user, even a windows switch triggers 1. I checked this with ProcessMonitor.

Another problem is that if I edit for example a package in the editor, the same happens, I thinks that every character gives a a lot of checks to git for the username. So editing is now a crime. And every change of windows, or a menu click does the same.

So my conclusion it must be something local, if you not encounter these problems. Thinking now of complete installing TOAD 12.8 and then beta.

Herald

9

Hey Herald,

This is a Git issue, which is a separate issue from your initial post. This issue (checking the Git login) was also in Toad 12.7 and 12.8. Nothing’s been changed in Toad 12.9 yet regarding Git. Are you saying this only started in beta 22? Did the problem not exist in Toad 12.8?

And just double-checking: you have tried it in beta 24?

-John

From: herald.ten.dam [bounce-heraldtendam@toadworld.com]

Sent: Friday, February 05, 2016 9:48 AM

To: toadoraclebeta@toadworld.com

Subject: RE: [Toad for Oracle - Beta Discussion Forum] Delay Editor and teamcoding (beta 22)

RE: Delay Editor and teamcoding (beta 22)

Reply by herald.ten.dam
John,

I downloaded latest now and will test again, but the problem I had in the 22 version and also in this new version is that TOAD when it starts up and connect to a schema which is under TeamCoding, he checks in git for the user the number of objects. I have 4000 objects under control in git, every time he issues an " git.ext config user.name" and this cost about 0.1 second. So I have to wait about 5 min before TOAD gives me some respond. On other occasions I see TOAD keeps checking for the user, even a windows switch triggers 1. I checked this with ProcessMonitor.

Another problem is that if I edit for example a package in the editor, the same happens, I thinks that every character gives a a lot of checks to git for the username. So editing is now a crime. And every change of windows, or a menu click does the same.

So my conclusion it must be something local, if you not encounter these problems. Thinking now of complete installing TOAD 12.8 and then beta.

Herald

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - Beta notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag
this post as spam/abuse.

10

Hi John,

yes since the 22 it got worse. Before I could normally edit and work in TOAD. The 24 had the same problems

I just now cleaned my machine from TOAD and reinstall now 12.8 and the 12.9 beta (24). Will see what happens. btw. I will also install a new version of GIT, we had just an old 1.9 version, so maybe that also will make things better.

Herald

11

Hey Herald,

I think I may have tracked this down. The rewrite surfaced an existing problem within the Git code. I’ve addressed the underlying problem, and I think this may fix the issue you’re seeing going forward. Feel free to give the next beta a shot and let me know if you’re still seeing this issue.

-John

From: herald.ten.dam [mailto:bounce-heraldtendam@toadworld.com]

Sent: Friday, February 05, 2016 9:48 AM

To: toadoraclebeta@toadworld.com

Subject: RE: [Toad for Oracle - Beta Discussion Forum] Delay Editor and teamcoding (beta 22)

RE: Delay Editor and teamcoding (beta 22)

Reply by herald.ten.dam

John,

I downloaded latest now and will test again, but the problem I had in the 22 version and also in this new version is that TOAD when it starts up and connect to a schema which is under TeamCoding, he checks in git for the user the number of objects. I have 4000 objects under control in git, every time he issues an " git.ext config user.name" and this cost about 0.1 second. So I have to wait about 5 min before TOAD gives me some respond. On other occasions I see TOAD keeps checking for the user, even a windows switch triggers 1. I checked this with ProcessMonitor.

Another problem is that if I edit for example a package in the editor, the same happens, I thinks that every character gives a a lot of checks to git for the username. So editing is now a crime. And every change of windows, or a menu click does the same.

So my conclusion it must be something local, if you not encounter these problems. Thinking now of complete installing TOAD 12.8 and then beta.

Herald

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - Beta notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag
this post as spam/abuse.

12

Hi John,

waiting for the next beta. I can now somehow workaround by cancelling the intermediate screen where I have to select a project. If I choose here a project, then I’ll have to wait and the editor will be slow afterwards, by cancelling the editor works normally.

Herald

13

Hi ohn,

the 25 beta is very nice. My login screen to vcs (git) is now also working. No extra git calls and the editor is working as intended. So I’m happy with this version (the 1th quick look :wink: ).

Thanks

Herald