If they have copied the data from a table in Excel, it will be in tab-delimited format in the clipboard. Typically the data will be provided in some kind of text format (CSV, tab delimited, fixed width) or binary file (XLS or XLSX). Depending on what exactly they mean by “upload this data” it may be reasonably easy to build or it could get quite complex. Of course, you know and I know that this is not necessarily a simple thing it is certainly not just an option to be enabled. Once they’ve finished with the data, odds are they’ll come back to you and ask “how do I upload this data back into APEX?” and expect that the answer is merely a flip of a switch to enable a built-in APEX feature. You can show them the excellent Interactive Report and Interactive Grid features of APEX, and train some of your users to use some of their capabilities, but at the end of the day, your users will still download the data into their spreadsheet software to do their own stuff with it.

You end statements in SQL*Plus with delimiters, and the default delimiter is a semicolon.Face it: your users are in love with Microsoft Excel, and you can’t do anything about it. Oh, and to answer the original question…īecause we’re trying to emulate SQL*Plus behavior. I say, when in doubt, back away from the tool, especially if you’re in production. What you need to be aware of is the differences and to learn new workflows if you are moving from other database tools to Oracle SQL Developer. In both cases you are being explicit with what is being sent to the database.Īgain, there’s not necessarily a ‘right’ or ‘wrong’ debate here. The parser looks for a query and keeps going until the statement is terminated with a semicolon – UNLESS it’s highlighted, then it assumes you only want to execute what is highlighted. See the statement at the cursor vs what SQL Developer actually executed? If you don’t highlight the text, here’s what you’ll see:

Highlight what you want executed, and hit Ctrl-Enter You can paste this same code into SQL Developer and run it without problems and without having to add semicolons to your statements. SQL Developer only executes what you ask it to execute If you were to try the same trick by running the delete statement, it would empty my entire BEER table instead of just trimming out the breweries from my home state. However, it is very important to understand how your tools work. The tool assumes that the blank line between it and the next statement, a DELETE, serves as a statement delimiter. In some tools, you can simply place your cursor on say the 2nd statement and ask to execute that statement.

Oracle apex sql statement separator