Type definitions for Discord Bot Maker by the DBM German community.
`@devrev/meerkat-dbm` is a browser-first database management layer built on [duckdb-wasm](https://github.com/duckdb/duckdb-wasm). It orchestrates query execution, manages DuckDB instances, caches files, persists data in browser storage, and optimizes memo
Helium protobuf definitions compiled to JS with TypeScript types
Dashboard for OHF Matter Server
A stand-alone types package for Undici
The ultimate javascript content-type utility.
Babel Types is a Lodash-esque utility library for AST nodes
Types for the AWS SDK
TypeScript definitions for express-serve-static-core
No description provided.
TypeScript definitions for @babel/core
Runtime type checking for React props and similar objects.
TypeScript definitions for prop-types
TypeScript definitions for express
Node.js utilities and TypeScript definitions for `package.json` and `tsconfig.json`
Types for Oxc AST nodes
Strip flow type annotations from your output code.
TypeScript definitions for trusted-types
Shared TypeScript definitions for Octokit projects
TypeScript definitions for eslint
Strict TypeScript and Flow types for style based on MDN data
TypeScript definitions for serve-static
Common token types for decoding and encoding numeric and string values
TypeScript definitions for node
Lite3::DBM is an object that behaves like a Ruby Hash but stores its data in a SQLite3 database table. It is a drop-in replacement for DBM. Values are optionally serialized with YAML or Marshal, allowing (almost) any Ruby type to be stored. In addition, there is rudimentary support for transactions with emphasis on simplicity and safety.
Lite3::DBM is an object that behaves like a Ruby Hash but stores its data in a SQLite3 database table. It is a drop-in replacement for DBM. Values are optionally serialized with YAML or Marshal, allowing (almost) any Ruby type to be stored. In addition, there is rudimentary support for transactions with emphasis on simplicity and safety. This is the JRuby version of dbmlite3; it is identical to the MRI version except for its dependencies.
== Ruby Data Objects If you're building something in Ruby that needs access to a database, you may opt to use an ORM like ActiveRecord, DataMapper or Sequel. But if your needs don't fit well with an ORM—maybe you're even writing an ORM—then you'll need some other way of talking to your database. RDO provides a common interface to a number of RDBMS backends, using a clean Ruby syntax, while supporting all the functionality you'd expect from a robust database connection library: * Consistent API to connect to various DBMS's * Type casting to Ruby types * Time zone handling (via the DBMS, not via some crazy time logic in Ruby) * Native bind values parameterization of queries, where supported by the DBMS * Retrieve query info from executed commands (e.g. affected rows) * Access RETURNING values just like any read query * Native prepared statements where supported, emulated where not * Results given using simple core Ruby data types == RDBMS Support Support for each RDBMS is provided in separate gems, so as to minimize the installation requirements and to facilitate the maintenace of each driver. Many gems are maintained by separate users who work more closely with those RDBMS's. Due to the nature of this gem, most of the nitty-gritty code is actually written in C. See the official README for full details.