10/9/2023 0 Comments Datagrip query historyTo do so, our new editor incorporates several key features that we felt we uniquely could provide. We still expect (and hope) our users will take their queries to explore and visualize on the third-party tools of their choice, but hope that we can help along the way in their quest to run familiar SQL on their messy data with as little pain as possible. With these challenges in mind, we decided to build our own SQL development environment from the ground up. Additionally, even seasoned SQL veterans might not be familiar with some of the array and object functions that we support. Traditional schema viewers struggle to represent this, especially when multiple types or nested arrays are involved. Document object model / Smart schemas (TLDR: Rockset ‘schemas' resemble more JSON objects than field lists): Fields can be nested within other fields or even within arrays.If a query editor fails to relate the multiple field types present in the field to the user, confusion can ensue. Strong dynamic typing (TLDR: many different types of data can live in a Rockset field at once): Despite its advantages, strong dynamic typing can lead to some puzzling query results. While these enable data queries that haven’t traditionally been feasible, they can also run against traditional query development workflows. And we built Rockset around two core principles: strong dynamic typing and the document object model. While Rockset supports standard ANSI SQL, we did add some extensions for arrays and object. nested JSON, Parquet, XML) was a novel concept to our users. Why ‘reinvent the wheel’ and create our own SQL development environment?ĭespite the quantity and quality of editors and dashboards available in the SQL community, we realized that using SQL on raw data (e.g. Datagrip, Jupyter, RStudio) and data exploration / visualization (e.g. Our users can easily integrate Rockset with a multitude of existing tools for SQL development (e.g. A SQL API allows our product to fit neatly into the stacks of our users without any workflow re-architecting. We love SQL - our mission is to bring fast, real-time queries to messy, semi-structured real-world data and SQL is a core part of our effort. Why build a new SQL development environment?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |