Parsing and internal parse structures — trees — are not something that development tools readily expose. It is assumed that most users are comfortable with numerous features that depend on parsing, such as formatting, code block collapsing/expanding, code advisors and so on, but aren’t really interested learning the formal code structure. In SQL Developer 4.2 we have attempted to encourage users to experiment with parse trees.
SQL Developer 4.2 early adopter release is out, but SQL performance analysis improvements somehow slipped from the list of additional features. The enclosed manuscript describes three small but valuable improvements:
– Cancelling Long Running Queries (while extracting partial statistics)
– Object Hyperlinks
I just finished reading Carl Safina's Beyond Words. It is the latest of a number of books (another great one is Out on a Limb by Ben Kilham) I have read that make it clear beyond any reasonable doubt that the individuals of many, many other species, including bears, octopuses, gorillas, chimpanzees, bonobos, crows, are turtles are self-aware; feel pain, sadness, joy; fear death; play; have individual personalities; work with tools; on and on and on.
Even though a space is a regular character, the client didn't want spaces at the beginning or end of a string. Any spaces in the middle were fine. Of course this could be handled by the application, but it must also be implemented in the database. Using a check constraint with a regular expression will prevent the end user from entering unwanted data.
To try things out, let's just start with a simple table with a single column.
"I eat using Uber-Eats.I push a button, the food is made, the driver delivers it to me. But when it's fully autonomous, how does the food actually get to my door? There's a tech stack that can get the car through the physical world to my doorstep, but then what? Does some robot get out of my car and deliver my food? That's hard.