#Sqlpro studio transpose full#

We’ll be releasing a more in-depth summary of current and planned features soon, but for now Transpose users can access the closed beta at .īeing able to share your favorite queries and use those created by the community unlocks the true potential of direct SQL access to Transpose.

The retro theme serves as a nod to computer terminals of times long gone. We’re calling this place The Playground - an environment built from the ground up to optimize the discovery of new views of blockchain data. That’s why we’re creating a unified experience for writing, testing, sharing, and exploring Transpose SQL queries. Greater query flexibility often means more complexity for end-users, especially when SQL is in the mix. We aim to supercharge the web3 development experience with this new level of flexibility.

#Sqlpro studio transpose full#

Long term, we are setting the stage for our community to create and share complex queries to take full advantage of the composability our data can offer.

It will immediately allow developers to make more focused, specific queries that minimize local post-processing and vastly speed up data retrieval.

Direct SQL access will do two things for those interacting with Transpose data: Adding new REST endpoints had a lot of overhead. We were unable to support many of your specialized asks if they didn’t fall within our intended use-cases. Despite having the most complete set of indexed data on Ethereum, enforcing a rigid REST interface meant end-user flexibility was limited. Like most APIs, Transpose has until now only been accessible via REST API. Most importantly, our indexing engine is highly extensible - name the protocol and we’ll reliably index and clean it. Inspired by the faults of players like The Graph, we’ve compiled the industry’s most standardized and complete data offering across the NFT and DeFi landscapes. Think RPC+1.Īt its core, Transpose is a blockchain indexing company. This means you can make real-time SQL queries in production, plug SQL queries into webhooks and websockets, and get responses from a service optimized for low-latency, high-speed, and live data access needs. Unlike existing blockchain data offerings, even those that offer SQL access, our API is designed to be directly integrated into your application. Read on to see how direct access to Transpose SQL can redefine the way you search, build, and analyze in web3. Since we want to retrieve the results for the 100 most recent queries, we’ll want to order by the sale timestamp in descending order.Writing your own complex SQL queries with joins and subqueries can be tricky - that’s why we’re also releasing The Transpose Atlas, a way for you to share and explore SQL queries that optimally achieve your goals.

Even queries without an explicit `ORDER BY` have an implicit order determined by the primary key of the table - however, specifying it explicitly makes things much clearer. Ordering is achieved with the `ORDER BY` clause. Ordering results is essential for defining what we want from a query. Let’s look into ordering and limiting to get more targeted results. This query would return every single BAYC sale that’s ever happened on Ethereum, and we can only return a limited amount of data per query. The following line will do the trick (don’t forget the single quotes around contract_address!): In this example, we’ll filter for sales where the contract address matches the BAYC address, but you can filter across any metric contained in any of the columns. We need to filter the results to only retrieve sales for the BAYC contract address.

`SELECT block_number, token_id, usd_price FROM ethereum.nft_sales`

For now we only support Ethereum mainnet but in the near future you’ll be able to do queries that join across tables from different chains.įor our example, we want to retrieve data from the nft_sales table: Note: All our tables are namespaced with the name of the chain they pull from. Things get especially powerful when you start combining data across different tables, but we’ll get to that in another post. You need to tell SQL which table you want to retrieve data from.