|
Replies:
15
-
Pages:
2
[
1
2
| Next
]
-
Last Post:
Jan 27, 2012 7:31 AM
by: Yoann
|
|
|
Posts:
6
Registered:
1/25/12
|
|
|
|
1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 25, 2012 9:13 AM
|
|
|
If external .sql file in SQL Script editor contains a big sql statement (for example package implementation with a lot of procedures), then after "Execute SQL Statement" scroll vertical position is changed and first line of SQL statement is made visible.
It is unwanted and confusing for user.
|
|
|
Posts:
117
Registered:
2/23/11
|
|
|
|
Re: 1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 25, 2012 9:58 AM
in response to: Vadim
|
|
|
Try using the stored procedure editor instead of the SQL worksheet for running package, function and procedure statements. It maintains your current vertical scroll position when compiling.
|
|
|
Posts:
6
Registered:
1/25/12
|
|
|
|
Re: 1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 25, 2012 10:49 AM
in response to: David H
|
|
|
Thanks David, I know that.
But I would like to use SVN to store all my sources. If I'll use sp editor, than my filesystem copy will be out of sync with database copy.
|
|
|
Posts:
6
Registered:
1/25/12
|
|
|
|
Re: 1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 25, 2012 3:29 PM
in response to: Vadim
|
|
|
David, thanks again!
I found what you did mean - it is possible to edit files using "pl*sql editor", which is not the same as "sql script editor".
|
|
|
Posts:
257
Registered:
10/11/10
|
|
|
|
Re: 1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 26, 2012 12:59 AM
in response to: Vadim
|
|
|
The same thing for me ...
I have a lot of stored procedures fore testing who are very long. And also a lot of Query's who are very long. I save anything with *.sql
If I open the QUERY.sql with SQL Editor I have the problem with the jump on first line on execute SQL Script. And executing in SP Editor doesn't works.
On opening die StoredProcedure saved as *.sql as default opens the SQL Editor where It always jumps to first line, on OPEN IN SP Editor what is not the default settings it want jump to first line.
For me is better to NEVER Jump to first line, but stay always at the actual line. If not, the alternatively is to have a property for it.
Michael
|
|
|
Posts:
559
Registered:
1/26/11
|
|
|
|
Re: 1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 26, 2012 1:07 AM
in response to: Vadim
|
|
|
Hi Vadim,
there are two editors for opening files. Files with .sql suffix are by default opened in the SQL Editor, files with other suffixes (.vw, .fnc, ...) are opened in the PL/SQL Editor.
SQL. (Note: default editors can be changed in Eclipse settings.)
For packages, we use suffix .pks (spec) or .pkb (body). The particular suffix is not as important, but you make sure that the file is opened on the correct editor.
Tomas
|
|
|
Posts:
559
Registered:
1/26/11
|
|
|
|
Re: 1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 26, 2012 1:12 AM
in response to: mburger
|
|
|
Michael, yes, I know, it is probably a common thing - anything regarding sql is saved as ".sql". I don't know if I understand your problem correctly, but I will test it.
I think if there is some problematic behaviour, it can surely be fixed.
Tomas
|
|
|
Posts:
257
Registered:
10/11/10
|
|
|
|
Re: 1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 26, 2012 2:53 AM
in response to: Tomas
|
|
|
I save anything which is not a package function or procedure as *.SQL
So anything I do, test query's or test store procedures I will save as *.SQL and will open in the SQL Editor.
And anything in the SQL Editor on execution will jump to first line, but I will never jump to first line.
Michael
|
|
|
Posts:
6
Registered:
1/25/12
|
|
|
|
Re: 1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 26, 2012 2:52 PM
in response to: Tomas
|
|
|
Tomas, thanks for your suggestion about default editors - I changed file extention and now correct editor opens by default.
Is it possible somehow to setup eclipse when I click on database object in schema browser to not open new sql object browser window, but navigate to file, which was used to generate this object.
If it is not possible, then it can be idea for toad: add a new lockable button in schema browser: "link to original file". If user checks this button - toad first may try to find definition of the object in workspace's files and navigate to it.
|
|
|
Posts:
257
Registered:
10/11/10
|
|
|
|
Re: 1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 27, 2012 12:05 AM
in response to: Vadim
|
|
|
The idea "link to original file" IS GREAT!!!!!!!!!!!!
I vote for it!
|
|
|
Posts:
58
Registered:
3/15/11
|
|
|
|
Re: 1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 27, 2012 1:08 AM
in response to: mburger
|
|
|
+1, this would be just perfect!
The whole thing I see for this is the following:
- Possibility to define the directory in wich are the objects (package Body, packeSpecs, ...)
- when ctrl-click on an object, instead of opening object from DB, open the file containing the object if found in the defeined directory.
The file name should be the same has the object name, case insensitive, free extention.
The reason I'm asking this is because we are using Clearcase with a directory structure alowing us to store both our ORACLE code and the other code, and the structure for the database code was made with another tool that doesn't have the same way of storing things as TEE.
If it's not the rigth place to put this, feel free to move to the correct place ;-)
Thanks a lot,
Yoann
|
Eclipse SDK Version: 3.7.2(32bit) Build id: M20120208-0800
-
TEE 1.8.0
-
Windows Seven(64bit)
-
JRE 1.6.0_27(32bit)
|
|
Posts:
559
Registered:
1/26/11
|
|
|
|
Re: 1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 27, 2012 1:21 AM
in response to: Vadim
|
|
|
Thank you guys. We will read and think about your ideas carefully
For now, I refer to the original issue - SQL Worksheet jumping to its top after execute. I registered this bug as TEE-195.
Tomas
|
|
|
Posts:
117
Registered:
2/23/11
|
|
|
|
Re: 1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 27, 2012 6:17 AM
in response to: Tomas
|
|
|
It sounds like we have two issues in this thread.
1) Tighter integration with version control.
2) The desired end scroll position of the SQL worksheet after execution.
I'm not sure I see either as a 'bug'. Wouldn't these be better suited for proposals in the Idea Pond where we can vote?
|
|
|
Posts:
58
Registered:
3/15/11
|
|
|
|
Re: 1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 27, 2012 6:35 AM
in response to: David H
|
|
|
certainly David,
The point 1, tighter integration with version control should go to the idea pond...
If I only knew where it is... If you can tell me, i'll move it there.
Thanks,
Yoann
|
Eclipse SDK Version: 3.7.2(32bit) Build id: M20120208-0800
-
TEE 1.8.0
-
Windows Seven(64bit)
-
JRE 1.6.0_27(32bit)
|
|
Posts:
117
Registered:
2/23/11
|
|
|
|
Re: 1.3.1 sql script editor - vertical scroll position is not saved on execute
Posted:
Jan 27, 2012 6:46 AM
in response to: Yoann
|
|
|
Thanks, Yoann.
The ideas link on the left side takes you there.
|
|
|
|
Legend
|
|
MVP: 2501
+
pts
|
|
Guru: 2001
- 2500
pts
|
|
Expert: 751
- 2000
pts
|
|
Enthusiast: 31
- 750
pts
|
|
Novice: 0
- 30
pts
|
|
Moderators
|
|
Helpful answer
(5 pts)
|
|
Answered
(10 pts)
|
|
