cola is a C implementation of the COLA structure described in the paper "Cache Oblivious Streaming B-Trees" by Bender, Farach-Colton, et al. This algorithm is a drop-in replacement for B-Tree databases/indexes which performs faster on spinning disks than B-Trees do on SSD. It's asymptotically optimal in terms of data transfers to and from disk. For example, random key inserts are turned into linear sequential writes while maintaining the property which queries always require, at most, precisely log N blocks read sequentially (but not contiguously) from disk (or half that, on average).
HOMER is a robust, carrier-grade, scalable SIP capturing system and monitoring application with hEP, IP Proto4 (IPIP) encapsulation, and port mirroring/monitoring support right out of the box, ready to process and store large amounts of signaling with instant searches, end-to-end analysis, and drill-down capabilities for ITSPs, VoIP providers, and trunk suppliers using SIP signaling.
epers stands for "Erlang persistence". As the name suggests, it tries to make it easy to use databases in Erlang programs, to make the language a little more agile, and (humbly) offer a nice adapter for several databases, hiding their implementation details (and the API of the library/framework/driver used to communicate with them). To achieve this, it aims to offer a somewhat consistent API to define and work with your model, while at the same not coupling your code too tightly to it.
pgFormatter is a SQL formatter/beautifier which supports keywords from SQL-92, SQL-99, SQL-2003, SQL-2008, and SQL-2011, and PostgreSQL-specific keywords. It can work as a console program or as a CGI system. It will automatically detect its environment and output as text or as HTML according to the context.
The YB.ORM library aims to simplify writing C++ code that has to deal with SQL databases. The goal is to provide a convenient interface like SQLAlchemy (Python) or Hibernate (Java). The library itself is cross-platform and supports a variety of SQL dialects: SQLite3, MySQL, Postgres, Oracle, and Firebird. Integration with Boost, Qt4, and wxWidgets is built-in. In a typical usage scenario, you would describe your database schema and table relationships in a simple XML-based format, generate SQL code to populate database schema with tables, generate C++ classes, add application-specific logic to the classes, and use these classes in cooperation with the Session object to query objects from the database, create new or modify/delete existing objects, or link and unlink objects using relations. Simple serialization to XML is supported along with connection pooling.
Barman (backup and recovery manager) for PostgreSQL is an administration tool for disaster recovery of PostgreSQL servers. It allows remote backups of multiple servers in business-critical environments and helps DBAs during the recovery phase. Barman's most-wanted features include backup catalogs, retention policies, remote recovery, archiving, and compression of WAL files and backups.
Network Inventory Lookup Assistant (NILA) is a combination network inventory database and lookup tool. It is designed to be compact and easily extensible to provide a custom solution for your network. The backend is a Perl CGI script which processes requests and returns output. It uses a SQL server for its storage and retrieval. The frontend is a Perl script which queries the HTTP backend and returns results. It is intended to be simple enough that you can take full advantage of its querying and updating abilities from a console or shell script.