Prototypes for all kind of data store, ie mongo, memory etc
Base driver class for Appium drivers
WebSocket protocol handler with pluggable I/O
Internals of neo4j-driver
OpenTelemetry instrumentation for `cassandra-driver` database client library for Apache Cassandra
The official MongoDB driver for Node.js
Implements the connection with the Neo4j Database using the Bolt Protocol
Applitools universal framework wrapper
Appium driver for Gecko-based browsers and web views
<!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section --> [badge-all-contributors]: https://img.shields.io/badge/all_contributors-3-orange.svg <!-- ALL-CONTRIBUTORS-BADGE:END --> [![typeorm-aurora-data-api-driver](https://circleci.com/g
SQLite client for Node.js applications with SQL-based migrations API written in Typescript
Android UiAutomator and Chrome support for Appium
UiAutomator2 integration for Appium
Microsoft SQL Server client for Node.js.
Appium driver for iOS using XCUITest for backend
Node.js driver for Snowflake
Universal Storage Layer
The official WebDriver JavaScript bindings from the Selenium project
A selenium server and browser driver manager for your end to end tests.
Prisma's driver adapter for "pg"
Apache Cassandra Node.js Driver
Internal set of utilities and types for Prisma's driver adapters.
Appium driver for Chromium-based browsers that work with Chromedriver
Appium driver for Safari browser
Sequel driver for Sandthorn
== 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.
Diff and patch tables
Diff and patch tables
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.
No description provided.