When export data in SQL Developer I get an extra pop up window that says "TOOL START" Export TOOL AT Date and Time. It does this for every export with a new window.
It's a bug.
For 18.4 you'll see complete export and other utilities information in the log panel.
It will show start time, number of records, stop time, and a link to the generated file.
Related
When I use the built-in Live Preview: Start Server and open dev tools (via the hamburger menu), I get lots of extra logs that don't occur in an external browser.
As I type console, for instance, when I type the c I get an error log c is not defined, then the same for co and con and cons all the way up until the word console is complete, filling up the devtools with nonsense logs. This does not happen in an external browser.
How can I suppress all these intermediary logs? I'd be happy with either a debouncing strategy, or a way to only refresh the page on save.
You could set an auto save delay.
Autosave has multiple modes. One of which is "afterDelay." If you set a delay, it will give you more time to type a line of code.
To make this change, you can set it like this:
Open the settings. It's under File > Preferences > Settings in Windows, or Code > Preferences > Settings in macOS.
Search for "autosave."
Change the Auto Save setting to afterDelay.
Change the Auto Save Delay setting to the number of milliseconds to wait before saving. For example, setting it to 5000 will delay the save for five seconds.
More information about configuring autosave.
is it possible to save the current state(all open windows, tabs, connections, files, etc...), shut down SQL Developer, restart it some other day and resume work where you left?
Yes, I've tried it with my SQL Developer Version 4.0.3.16 Build MAIN-16.84
Every time you close SQL Developer while some tabs opened, it will opened those tabs again when you open SQL Developer again
However, SQL Developer won't remember the connections you used to execute those SQLs. So when you try to execute those SQLs, you will prompted to choose the connection where the SQL will be executed
nb : you can also open recent files by using Navigate -> Go To Recent Files
Just to add to nobodykid's answer: It seems to me that open tabs with queries in are not displayed at next session unless they are stored to a file on disk explicitly by the user.
In other words, if you close SQL developer and you do not save your tabs as files on disk explicitly, the tabs will not be recovered upon restart.
I'm sure that I'm making some kind of rookie mistake, but I'm using EclEmma for the first time right now and can't figure out, despite checking numerous guides, how to export my coverage report. For reference, this is on Windows 8 x64 and using Eclipse Kepler (let me know if you need any more information than that).
I can see that the EclEmma has successfully run, and I can get into and play with the Coverage view as below:
However, right-clicking anywhere in the report offers only an option to "Export Session," never "Export Report," and going through my File -> Export dialog doesn't seem to do any better. I tried exporting the session as XML and a few different configurations, but it never got the code coverage report that I was looking for.
Is there something I'm doing wrong or need to ensure before I can export it? Thanks in advance.
As you do before, click right button and select "Export Session".
Type "report" and you can find the "coverage report" option.
Click "next"
You can get the Export report panel.
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 remember watching a webcast from Mark Russinovich showing the sequence of keyboard keys for a user initiated kernel dump. Can somebody refresh my memory on the exact order of the keys.
Please note this is for XP.
http://psacake.com/web/jr.asp contains full instructions, and here's an excerpt:
While it may seem odd to think about purposefully causing a Blue Screen Of Death (BSOD), Microsoft includes such a provision in Windows XP. This might come in handy for testing and troubleshooting your Startup And Recovery settings, Event logging, and for demonstration purposes.
Here's how to create a BSOD:
Launch the Registry Editor (Regedit.exe).
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters.
Go to Edit, select New | DWORD Value and name the new value CrashOnCtrlScroll.
Double-click the CrashOnCtrlScroll DWORD Value, type 1 in the Value Data textbox, and click OK.
Close the Registry Editor and restart Windows XP.
When you want to cause a BSOD, press and hold down the [Ctrl] key on the right side of your keyboard, and then tap the [ScrollLock] key twice. Now you should see the BSOD.
If your system reboots instead of displaying the BSOD, you'll have to disable the Automatically
Restart setting in the System Properties dialog box. To do so, follow these steps:
Press [Windows]-Break.
Select the Advanced tab.
Click the Settings button in the Startup And Recovery panel.
Clear the Automatically Restart check box in the System Failure panel.
Click OK twice.
Here's how you remove the BSOD configuration:
Launch the Registry Editor (Regedit.exe).
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters.
Select the CrashOnCtrlScroll value, pull down the Edit menu, and select the Delete command.
Close the Registry Editor and restart Windows XP.
Note: Editing the registry is risky, so make sure you have a verified backup before making any changes.
And I may be wrong in assuming you want BSOD, so this is a Microsoft Page showing how to capture kernel dumps:
https://web.archive.org/web/20151014034039/https://support.microsoft.com/fr-ma/kb/316450
As far as I know, the "Create Dump" command was only added to Task Manager in Vista. The only process I know of to do this is using the adplus VBScript that comes with Debugging Tools. Short of hooking into dbghelp and programmatically doing it yourself.
You can setup the user dump tool from Microsoft with hot keys to dump a process. However, this is a user process dump, not a kernel dump...
I don't know of any keyboard short cuts, but are you looking for like in task manager, when you right click on a process and select "Create Dump"?