I have a take home project, I have to connect to a Postgres SQL, run some queries, make changes to a repo and push my changes. I have successfully connected to the database (I'm able to see everything when I select the elephant and I have it selected at the bottom of my screen). When I write a simple code and execute, I get both message "Query Completed in 4.2 sec." and "Waiting for query to complete"
After a while, I get an error message that the window is not responding, you can reopen the window or keep waiting". Everything should be up to date (I downloaded the latest software as of Sept 1st 2022). What step am I missing? I was expecting the results of my query.
Please let me know what to check
The query needs to be saved (Ctrl + S for Windows) before the query can be executed.
Related
I've just run a couple of queries where I forgot to click on the blue 'refresh' button when I launched Oracle SQL Developer.
But I was wondering whether it actually refreshes anyway, when you actually launch it?
Short answer: 'no.'
But first, let's share with folks with the 'blue refresh button' you mention in your question.
What does this button do?
It re-executes the query that the resultset is tied to, in this case
select * from employees
When you restart/re-open SQL Developer it does not even connect to any databases, much less re-execute any queries automatically.
What you might see is a .SQL file re-opened as you had it open when you closed the application from your last session. But no database work will happen until you hit the 'Connect' button.
Disclaimer: I work for Oracle and am the product manager for SQL Developer.
I have a large query I am running in Oracle SQL Developer. The query seemed to run successfully and then I made the mistake of hitting count rows and it froze. I had to terminate the program in the task manager. I have been searching online and I have seen a lot about how unsaved scripts can be recovered using history, but I dont see anything about restoring the query result. Is it cashed anywhere so I dont have to run the query all over again?
Any help is greatly appreciated.
If you are using PL/SQL Developer, then you need to press CTRL+E. You can find Recent Executed Quer
Okay, this is kind of odd and it is driving us nuts. I'll outline what is going on as best I can, then I can provide specific details and/or code as folks request it, because I'm not sure what will be needed to suss this out.
I have an access database I have built so our analysts can work within a queue, select records, do whatever research is needed, then either mark the record in question as okay, or fill in some blanks and mark it as needing a dispute (we work in billing).
Basically, the database opens and a hidden form pulls the NT User Name from the local machine, then opens a visible form that queries the database via SQL ODBC to display a list of records with that NT User Name attached to them.
The user can then scroll through the records, select them to get more information, and click a button to mark them as okay, or another to mark them as needing a dispute.
If they click the okay button, it fires off an update query to mark the record as okay. If they click the dispute button, then it opens a third form to show them the line item they are disputing with values from all of the other text fields on the form that they can select from/fill in. On that form there is a button to commit the dispute, which fires off another query to update the values into the same table as the 'okay' button.
So, the issue is, that this all works perfectly on my workhorse machine, and an essentially naked test machine. It also works on another co-worker's machine. However, whenever we try to run it on two other coworkers' machines, everything works just fine, except for any of the queries that attempt to write back to the ODBC connection. All of the read-only stuff works just fine, just not the updates. But the updates work perfectly, and super-fast on my machine, my test rig, and my other co-worker's machine.
We've tried reinstalling the ODBC connection, and the ODBC SQL Drivers.
No go.
We've tried just opening the table in question on the affected machines and making direct edits to the table.
This works if no forms are open in the database, but as soon as we open a form, no update query will run against the table.
So, we tried commenting out all code on all open forms except the docmd.openquery code for the single button we used to test the update query.
No go.
We even built a new form with just a button on it that triggers a new update query that makes only one simple update (Now()) to the table in question.
This runs fine on its own, but times out when run off the button click from the form.
We tried changing the MS Office install on one machine to 'run all from computer' to make sure all necessary components are installed/present.
No go.
We tried installing the ODBC connection both via the normal windows interface, and through the access linked table manager interface.
No go.
We tried installing both 64-bit and 32-bit ODBC connections, both under USER DSN and SYSTEM DSN, and all permutations of one and not the other that we could think of.
No go.
It seems that no update query will write to that table while any form is open, but works just fine with no forms open. But only on these other two machines. Everything works fine on the other three machines we've tested on, whether forms are open or not.
We're kind of at wit's end here and don't know where to go. Google is proving unhelpful, possibly because we just don't know exactly how to search the problem out.
Here's basic technical stuff and I am happy to provide whatever other details, code, queries, etc. that are needed to troubleshoot upon request:
OS: Windows 7 Enterprise 64-bit
Software: MS Office Enterprise 2013 32-bit
ODBC: SQL Server
All users have admin access to their respective machines.
Turns out that the issue here seems to have been an intermittent issue with Access being unable to determine which record to update due to the way we were calling details from a continuous form.
We went back to formula on our UI and built it so there is only ever one record on a form when we try to make changes to records, so there can be no system confusion about what record to update.
Still no clue as to why it was working intermittently, but the new iteration is working now.
Thank you all for your questions and suggestions. :)
Does eclipse remember when a program was executed last time? I know there is run configurations, but that doesn't keep track of past executions and their order of execution.
When a program is executed at the shell, then shell keeps tracks of the order of their executions? I want similar utility in eclipse along with the time of execution.
You can see in the debug view or in the console view (click the arrow near screen icon) the program that have run and the start time.
Edit : In Preferences/(Run/Debug)/Launching uncheck the "Remove termined launches when a new launch is created".
This list is reset if you clear hit or if you close Eclipse.
If you want a more permanent information, I think your programs should log that info in files.
you can execute your previous most recent program with ctrl+f11. For detail you can go to run->run history.
If you need the time when your program was executed, make your program output the time by itself. There is nothing in Eclipse that can do exactly what you need.
I am very new to Eclipse. I am trying to do a basic remote search in my C:/SomeFolder drive using CTRL+H, however whenever I perform the search, the search gets cancelled automatically after 2 seconds or so. Do you know why this is happening and how I can fix that?
I had "Search archive files" selected. Once I unchecked it, everything worked fine.