SQL patch migration tool
Utilities for SQL instrumentations
A RESTful API for managing your Postgres.
Format whitespace in a SQL query to make it more readable
Fix broken node modules with no fuss
A simple and lightweight library for highlighting SQL queries written in pure JavaScript
PGlite is a WASM Postgres build packaged into a TypeScript client library that enables you to run Postgres in the browser, Node.js and Bun, with no need to install any other dependencies. It is only 3.7mb gzipped.
Enhance ESLint with better support for large scale monorepos
A JavaScript library for connecting securely to your Cloud SQL instances
Fast implementation of JSON-Patch (RFC-6902) with duplex (observe changes) capabilities
🛡️ Faster SQL escape and format for JavaScript (Node.js, Bun, and Deno).
SQL language support for the CodeMirror code editor
simple node sql parser
A TDS driver, for connecting to MS SQLServer databases.
Simple SQL escape and format for MySQL
A package/program to help patch MySql databases
npm package for https://github.com/google/diff-match-patch
Microsoft SQL Server client for Node.js.
Patch console methods to intercept output
TypeScript definitions for diff-match-patch
Robust diff, match and patch algorithms to perform operations required for synchronizing plain text
Summarize any SQL query
Driver for connection to Databricks SQL via Thrift API.
Generates a set of Sanity patches needed to change an item (usually a document) from one shape to another
Patched(see https://github.com/norikra/fluent-plugin-norikra/issues/7). process events on fluentd with SQL like query, with built-in Norikra server if needed.
activerecord-jdbc-adapter is a database adapter for Rails\' ActiveRecord component that can be used with JRuby[http://www.jruby.org/]. It allows use of virtually any JDBC-compliant database with your JRuby on Rails application. Includes patch by cmoran92 to eliminate duplicates when SELECTing DISTINCT with JOINS on MS SQL Server.
Sequel `:d1` adapter and Opal compatibility patches for Cloudflare D1. Pass a duck-typed D1 binding to `Sequel.connect(adapter: :d1, d1: binding)`. Includes the `homura db:migrate:*` tooling to compile Sequel migration DSL to wrangler SQL.
The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `<` lower than - `>=` lower than or equal - `><` included in list, items should be separated by `|` - `!><` not included in list, items should be separated by `|` - `~` pattern matching, may include `%` (any characters) and `_` (one character) - `!~` pattern not matching, may include `%` (any characters) and `_` (one character)
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.