Below you'll find a list of all posts that have been tagged as “formatter”
A follower reached out to me late yesterday with this request: And the answer is yes, we can pretty much get there. I’ve noticed a few things by looking at his hand-formatted code on the bottom section. He prefers: everything lowercase right-aligned keywords no line breaks for the sub query ()’s no line breaks after SELECT/FROM/WHERE keywords So let’s go …
Due to popular demand, we’ve added this new preference to the formatter. With it turned on: On SELECT B.DEPARTMENT_NAME, A.FIRST_NAME, A.LAST_NAME, A.SALARY FROM DEPARTMENTS B, EMPLOYEES A WHERE A.EMPLOYEE_ID = B.MANAGER_ID AND B.DEPARTMENT_ID (+) = A.DEPARTMENT_ID ORDER BY SALARY DESC, LAST_NAME ASC; Off SELECT B.DEPARTMENT_NAME, A.FIRST_NAME, A.LAST_NAME, A.SALARY FROM DEPARTMENTS B, EMPLOYEES A WHERE A.EMPLOYEE_ID = B.MANAGER_ID AND B.DEPARTMENT_ID (+) …
For 17.4, the formatter will attempt to format invalid SQL for you. If the parser runs into a problem recognizing your code, it will format it as much as it can. But that’s not all. It will ALSO go to the end of your statement, and traverse the SQL in the other direction and continue formatting as far as it …
“I do not want a line break after the and statement.” I’ve seen this come up a few times, so let’s answer that right now. SELECT 1 FROM dual WHERE 1=2 AND 2=3 AND 3=4 Default formatting changes that to SELECT 1 FROM dual WHERE 1 = 2 AND 2 = 3 AND 3 = 4 This is NOT what …
Just because you’re in a command line interface doesn’t mean you’re stuck with ugly code! Wait, if it’s my code, you’re stuck with ugly code. But if it’s YOUR code, then you’re not stuck with poorly formatted code. You can of course use the FORMAT command to format what’s in a file or in the SQLcl buffer. I don’t like …
Tons of bugs fixes based on your feedback, especially with the formatter. A few more changes with the formatter: we added more preferences for more flexibility we let you submit code to ‘shape’ the formatting preferences automatically we exposed the brains of the formatter so you can do pretty much whatever you want An example of the formatter ‘by example’ …
For some reason I procrastinated setting up my video software on my new work machine. Big mistake. I put together this animated GIF to show some new things in version 4.2: Updated formatter – better support for ANSI joins Opening objects referenced in your execution plans Inserting Hints Not new but underutilized: how to compare plans/AutoTraces One Last Thing… …don’t …
The old formatter, the code that’s used to format your code from v1 to version 4.1 was based on some pattern matching code and expressions. It was very limited, and didn’t like a lot of syntax and coding styles common in Oracle code. It also wasn’t very flexible. So we built a new engine. One that takes advantage of our …
Not to start a religious war, but white space in your code can cause havoc when you’re doing code compares and versioning. Some folks like tabs, others prefer to control how their code looks regardless of the editor’s tab display options. From what I can tell, SQL Developer’s code editors won’t even let you insert a tab into them – …
This post is a tease. It’s also a request. Send me your ugly code. In version v4.2 of SQL Developer – to be released in calendar year 2016 – we’ll be offering a new formatter for your SQL and PL/SQL. It’s got a completely new engine under the hood. It’s faster. It’s more efficient. And it sounds really cool too …