DataDraw is an ultra-fast persistent database for high performance programs written in C. It's so fast that many programs keep all their data in a DataDraw database, even while being manipulated in inner loops of compute intensive applications. DataDraw databases are compiled, and directly link into your C programs. DataDraw databases are resident in memory, making data manipulation even faster than if they were stored in native C data structures (really). DataDraw databases can be persistent. Modifications to persistent data are written to disk as they are made, which of course dramatically slows write times. However, DataDraw databases can also be volatile. Volatile databases exist only in memory, and only for the duration that your program needs it. Volatile databases can be directly manipulated faster than C structures, since data is better organized in memory to optimize cache performance DataDraw supports modular design. An application can have one or more common persistent databases, and multiple volatile databases to support various tools' data structures. Classes in a tool's database can extend classes in the common database. DataDraw is also 64-bit optimized, allowing programs to run much faster and in less memory than standard C programs using 64-bit pointers. This is because DataDraw databases supports over 4 billion objects of a given class with 32-bit object references.
OS | Architecture | Version |
---|---|---|
NetBSD 10.0 | aarch64 | datadraw-3.1.1.tgz |
NetBSD 10.0 | aarch64 | datadraw-3.1.1.tgz |
NetBSD 10.0 | aarch64eb | datadraw-3.1.1.tgz |
NetBSD 10.0 | aarch64eb | datadraw-3.1.1.tgz |
NetBSD 10.0 | alpha | datadraw-3.1.1.tgz |
NetBSD 10.0 | alpha | datadraw-3.1.1.tgz |
NetBSD 10.0 | earmv6hf | datadraw-3.1.1.tgz |
NetBSD 10.0 | earmv6hf | datadraw-3.1.1.tgz |
NetBSD 10.0 | earmv6hf | datadraw-3.1.1.tgz |
NetBSD 10.0 | earmv7hf | datadraw-3.1.1.tgz |
NetBSD 10.0 | earmv7hf | datadraw-3.1.1.tgz |
NetBSD 10.0 | earmv7hf | datadraw-3.1.1.tgz |
NetBSD 10.0 | i386 | datadraw-3.1.1.tgz |
NetBSD 10.0 | i386 | datadraw-3.1.1.tgz |
NetBSD 10.0 | powerpc | datadraw-3.1.1.tgz |
NetBSD 10.0 | powerpc | datadraw-3.1.1.tgz |
NetBSD 10.0 | powerpc | datadraw-3.1.1.tgz |
NetBSD 10.0 | sh3el | datadraw-3.1.1.tgz |
NetBSD 10.0 | sh3el | datadraw-3.1.1.tgz |
NetBSD 10.0 | sparc64 | datadraw-3.1.1.tgz |
NetBSD 10.0 | sparc64 | datadraw-3.1.1.tgz |
NetBSD 10.0 | sparc | datadraw-3.1.1.tgz |
NetBSD 10.0 | sparc | datadraw-3.1.1.tgz |
NetBSD 10.0 | vax | datadraw-3.1.1.tgz |
NetBSD 10.0 | vax | datadraw-3.1.1.tgz |
NetBSD 10.0 | vax | datadraw-3.1.1.tgz |
NetBSD 10.0 | x86_64 | datadraw-3.1.1.tgz |
NetBSD 10.0 | x86_64 | datadraw-3.1.1.tgz |
NetBSD 9.0 | aarch64 | datadraw-3.1.1.tgz |
NetBSD 9.0 | aarch64 | datadraw-3.1.1.tgz |
NetBSD 9.0 | alpha | datadraw-3.1.1.tgz |
NetBSD 9.0 | alpha | datadraw-3.1.1.tgz |
NetBSD 9.0 | earmv6hf | datadraw-3.1.1.tgz |
NetBSD 9.0 | earmv6hf | datadraw-3.1.1.tgz |
NetBSD 9.0 | earmv6hf | datadraw-3.1.1.tgz |
NetBSD 9.0 | earmv7hf | datadraw-3.1.1.tgz |
NetBSD 9.0 | earmv7hf | datadraw-3.1.1.tgz |
NetBSD 9.0 | earmv7hf | datadraw-3.1.1.tgz |
NetBSD 9.0 | i386 | datadraw-3.1.1.tgz |
NetBSD 9.0 | i386 | datadraw-3.1.1.tgz |
NetBSD 9.0 | m68k | datadraw-3.1.1.tgz |
NetBSD 9.0 | powerpc | datadraw-3.1.1.tgz |
NetBSD 9.0 | powerpc | datadraw-3.1.1.tgz |
NetBSD 9.0 | powerpc | datadraw-3.1.1.tgz |
NetBSD 9.0 | sparc64 | datadraw-3.1.1.tgz |
NetBSD 9.0 | x86_64 | datadraw-3.1.1.tgz |
NetBSD 9.0 | x86_64 | datadraw-3.1.1.tgz |
NetBSD 9.3 | x86_64 | datadraw-3.1.1.tgz |
Binary packages can be installed with the high-level tool pkgin (which can be installed with pkg_add) or pkg_add(1) (installed by default). The NetBSD packages collection is also designed to permit easy installation from source.
The pkg_admin audit command locates any installed package which has been mentioned in security advisories as having vulnerabilities.
Please note the vulnerabilities database might not be fully accurate, and not every bug is exploitable with every configuration.
Problem reports, updates or suggestions for this package should be reported with send-pr.