Back to Blog
Oracle sql developer query builder5/28/2023 ![]() ![]() The good news is, we have a new release every 3 months now, so tweaks, fixes, and improvements are never that far away. If I’m wrong, here’s your chance to tell me. I think we’ve found a good compromise here…especially if my assumption that many folks will use the Query Builder for existing queries. I’d like to have our cake and eat it too, but I also need to make game-time decisions and try to make for the best user experience. The Query Builder functionality allows you to visually build queries of any complexity, easily find and filter database objects, build relationships between. We could try to refactor the 3rd party vendor’s bad SQL, but every time we do that, upgrades get much trickier. Here, let me show you how I mean: I really like this. You can also just drag and drop the queries to the worksheet FIRST, say YES to the JOINS, then toggle to the Query Builder. Here’s the option to disable if you want the magic, auto joins back. It just also means, that now you need to draw or code the joins yourself. So in 18.3, we don’t do that, and the Query Builder renders in a second or less for more queries. The easiest solution was to ‘nuke’ those ‘bad fk lookup queries.’ It was slow to the point of users wouldn’t give it a 2nd try, and I wouldn’t reccommend they even try it in the first place. While that was a nice feature, it just cost too much. It would ‘draw the pretty lines for you’, and it would give you a list of related objects for each table. Well, the folks that build the solution (it’s a 3rd party library that we have licensed) had some pretty gnarly queries used that do look-ups on the table to find foreign keys and ‘related’ tables. So slow, that I didn’t recommend to people that they should use it anymore. Lifetime access to 100+ courses in all technologies in one subscription like Data Science, Blockchain, Iot, Digital marketing, Full stack development & etc. And dragging and dropping new tables into a query could take 10 seconds, each time you did it. It could take 30 or more seconds to visually render an existing query. The query builder is also useful for helping build a ‘picture’ of your queries. I guarantee this tip will save you time if you’re joining 3 or more tables 6. You can then toggle over to the Query Builder to toggle off the columns you don’t want to query. I advocated that users do a combination of both, especially if they were new to SQL in general. SQL Developer will auto-join the related objects. And it would allow you to build queries from scratch, by dragging and dropping them into the query builder design area. The query builder would allow you to reverse engineer a query in a worksheet to a visual representation. So who paid for these performance gains? We disabled one of its primary features.īut first, let’s take a step a back and explain the scenario. One of the improvements for version 18.3 was a much improved, performant query builder. ![]()
0 Comments
Read More
Leave a Reply. |