LDB(3)

📦
version 4.24.7 · 22 versions
, in fedora 44

✨ NAME ✨

ldb — a light-weight database library 💅

okay bestie, buckle up, because this one is literally the moment a whole database library gets introduced to you and honestly? she's iconic.

🌈 SYNOPSIS 🌈

#include <ldb.h>

that's it. that's the whole vibe. one include and you're in 🫶

💖 DESCRIPTION 💖

ldb is a light weight embedded database library and API. With a programming interface that is very similar to LDAP, ldb can store its data either in a tdb(3) database or in a real LDAP database. two options, zero drama ✨

when you're using it with the tdb backend, ldb does not require any database daemon. nope, none, she's independent 💅 instead, ldb function calls are processed immediately by the ldb library, which does IO directly on the database, while allowing multiple readers/writers using operating system byte range locks. and the way that gives you an API with very low overheads — often resulting in speeds of more than 10x what can be achieved with a more traditional LDAP architecture. ten times. TEN. that's not a glow-up, that's a glow-up 🌟

in a taxonomy of databases, ldb would sit half way between key/value pair databases (such as berkeley db or tdb) and a full LDAP database. like, she's in her in-between era and she's thriving. with a structured attribute oriented API like LDAP and good indexing capabilities, ldb can be used for quite sophisticated applications that need a light weight database, without the administrative overhead of a full LDAP installation. sophisticated and low-maintenance, the dream fr fr 😌

included with ldb are a number of useful command line tools for manipulating a ldb database. these tools are similar in style to the equivalent ldap command line tools 👑

in its default mode of operation with a tdb backend, ldb can also be seen as a "schema-less LDAP". by default ldb does not require a schema, which greatly reduces the complexity of getting started with ldb databases. no schema, no stress, no 47-page config file, we love to see it 🎀 as the complexity of you application grows you can take advantage of some of the optional schema-like attributes that ldb offers, or you can migrate to using the full LDAP api while keeping your exiting ldb code. (yes, "exiting" — that's the original's typo, not mine, and I will not be correcting her, she's doing great 🥰) so you can level up whenever, and your existing code comes with you. no cap.

if you are new to ldb, then I suggest starting with the manual pages for ldbsearch(1) and ldbedit(1), and experimenting with a local database. then I suggest you look at the ldb_connect(3) and ldb_search(3) manual pages. that's the starter pack bestie, go play 🌸

🛠️ TOOLS 🛠️

the little command-line besties that come with her:

  • ldbsearch(1) — command line ldb search utility 🔍
  • ldbedit(1) — edit all or part of a ldb database using your favourite editor ✏️
  • ldbadd(1) — add records to a ldb database using LDIF formatted input ➕
  • ldbdel(1) — delete records from a ldb database 🗑️
  • ldbmodify(1) — modify records in a ldb database using LDIF formatted input 🔧

💅 FUNCTIONS 💅

the whole function family, and yes, every single one of them is here, I'm not skipping a single cousin at this reunion:

  • ldb_connect(3) — connect to a ldb backend 🔌
  • ldb_search(3) — perform a database search 🔍
  • ldb_add(3) — add a record to the database ➕
  • ldb_delete(3) — delete a record from the database 🗑️
  • ldb_modify(3) — modify a record in the database 🔧
  • ldb_errstring(3) — retrieve extended error information from the last operation 🚨
  • ldb_ldif_write(3) — write a LDIF formatted message 📝
  • ldb_ldif_write_file(3) — write a LDIF formatted message to a file 📁
  • ldb_ldif_read(3) — read a LDIF formatted message 📖
  • ldb_ldif_read_free(3) — free the result of a ldb_ldif_read() 🧹
  • ldb_ldif_read_file(3) — read a LDIF message from a file 📂
  • ldb_ldif_read_string(3) — read a LDIF message from a string 🧵
  • ldb_msg_find_element(3) — find an element in a ldb_message 🔎
  • ldb_val_equal_exact(3) — compare two ldb_val structures ⚖️
  • ldb_msg_find_val(3) — find an element by value 💎
  • ldb_msg_add_empty(3) — add an empty message element to a ldb_message 🫙
  • ldb_msg_add(3) — add a non-empty message element to a ldb_message 📦
  • ldb_msg_element_compare(3) — compare two ldb_message_element structures 🆚
  • ldb_msg_find_int(3) — return an integer value from a ldb_message 🔢
  • ldb_msg_find_uint(3) — return an unsigned integer value from a ldb_message 🔢
  • ldb_msg_find_double(3) — return a double value from a ldb_message 🔢
  • ldb_msg_find_string(3) — return a string value from a ldb_message 🔤
  • ldb_set_alloc(3) — set the memory allocation function to be used by ldb 🧠
  • ldb_set_debug(3) — set a debug handler to be used by ldb 🐛
  • ldb_set_debug_stderr(3) — set a debug handler for stderr output 🖥️

🌿 ENVIRONMENT VARIABLES 🌿

the ones that change her behaviour behind the scenes:

  • LDB_URL — connect to the provided URL (cmdline tools only)
  • LDB_MODULES_PATH — path where to load ldb modules from
  • LDB_MODULES_ENABLE_DEEPBIND — enable RTLD_DEEPBIND when loading ldb modules

👑 AUTHOR 👑

ldb was written by Andrew Tridgell[1]. absolute legend behaviour, we stan 💜

if you wish to report a problem or make a suggestion then please see the http://ldb.samba.org/ web site for current contact and maintainer information. they want to hear from you, fr fr 🫶

ldb is released under the GNU Lesser General Public License version 2 or later. please see the file COPYING for license details. legal but make it slay 📜✨

🦋 NOTES 🦋

  1. Andrew Tridgell https://www.samba.org/~tridge/

and that's the whole page bestie!! this was LDB 1.1, dated 09/09/2026, from the System Administration tools section of the manual — mwah, go forth and query something 💖🎀🦋

📦 where this page comes from