Habib's Byte Hub

Hello fellas!! 👋 Today's topic: Understanding the REST-Enabled SQL Service in ORDS and How to Customize its Response Format. REST-Enabled SQL Service in ORDS What is it? The REST-Enabled SQL service is an HTTPS web service that provides access to the Oracle Database SQL engine. You can POST SQL statements to the service. The service then runs the SQL statements against Oracle Database and returns the result to the client in a JSON format. Example: Making a Request When making a request to the REST-Enabled SQL Service, you typically get a response by default that looks like this: Sample Request curl --location 'http://localhost:8086/ords/<schema_alias>/_/sql' \ --header 'Content-Type: application/json' \ -u "user:dummySecret" \ --data '{ "statementText": "select sysdate from dual" }' Default Response Format ...

ORDS vs C# for Building REST APIs: Which is Easier? If you've ever built REST APIs using commonly used programming languages, you know the drill: create models, wire up a controller, connect to a database, map DTOs, validate, inject dependencies… and that's before you even touch the security aspect of the API. 😅 Being a past C# lover, I started questioning how easy it was to build REST APIs in ORDS compared to C#. Spoiler: ORDS is crazy simple for the basics. Let me show you a side-by-side comparison using the same use case, managing a Country table, without diving into security (we'll ignore auth and tokens and just focus on the REST experience). Use Case We want to expose the following operations via REST: GET /countries — list all countries GET /countries/{id} — get one country POST /countries — create a new country ...

Hey folks! Today, I want to introduce you to a tool that’s been part of my daily grind: Oracle REST Data Services, or ORDS. So, What’s ORDS? Basically, ORDS is a tool that lets you expose your Oracle database data as RESTful APIs. Instead of wrestling with complex backend code, ORDS makes it super easy to build and deploy APIs. With ORDS, your data becomes accessible from anywhere with just a few HTTP calls. Think of it as giving your database a direct, web-friendly voice. Users and ORDS interaction workflow Why ORDS? 🌟 Imagine this: You’ve got an Oracle database packed with valuable data, and you want to make it accessible to an app, a web service, or another system. Usually, you’d need a whole backend to handle data retrieval, authentication, response formatting… you name it. But with ORDS? You just set it up, map it to your database tables or procedures, and voilà—you’ve got an API that you can call from anywhere. Here’s why ORDS is a game-...