File: control

package info (click to toggle)
tntdb 1.3-4
  • links: PTS
  • area: main
  • in suites: bullseye, buster, sid, stretch
  • size: 3,048 kB
  • ctags: 2,387
  • sloc: cpp: 14,250; sh: 11,084; makefile: 251; ansic: 144; sql: 106
file content (84 lines) | stat: -rw-r--r-- 3,647 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
Source: tntdb
Section: libs
Priority: optional
Maintainer: Kari Pahula <kaol@debian.org>
Build-Depends: cdbs, debhelper (>= 9), libcxxtools-dev (>= 2.2.1-2), libsqlite3-dev, default-libmysqlclient-dev, libpq-dev, libltdl-dev, doxygen, dh-autoreconf, sqlite3
Build-Conflicts: libtntdb-dev, libtntdb3
Standards-Version: 3.9.8
Homepage: http://www.tntnet.org/tntdb.html

Package: libtntdb4v5
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Recommends: tntdb-mysql4v5|tntdb-postgresql4v5|tntdb-sqlite4v5
Suggests: tntdb-mysql4v5, tntdb-postgresql4v5, tntdb-sqlite4v5, libtntdb-dev
Breaks: libtntdb4
Replaces: libtntdb4
Description: C++ class library for easy database access
 This library provides a thin, database independent layer over an SQL
 database.  It lacks complex features like schema queries or wrapper
 classes like active result sets or data bound controls.  Instead you
 get to access the database directly with SQL queries.  The library is
 suited for application programming, not for writing generic database
 handling tools.
 .
 Currently has support for MySQL, PostgreSQL and SQLite.

Package: tntdb-mysql4v5
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Breaks: libtntdb-mysql4
Replaces: libtntdb-mysql4
Description: MySQL backend for tntdb database access library
 This library provides a thin, database independent layer over an SQL
 database.  It lacks complex features like schema queries or wrapper
 classes like active result sets or data bound controls.  Instead you
 get to access the database directly with SQL queries.  The library is
 suited for application programming, not for writing generic database
 handling tools.
 .
 This file has the necessary files for MySQL support.

Package: tntdb-postgresql4v5
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Breaks: libtntdb-postgresql4
Replaces: libtntdb-postgresql4
Description: PostgreSQL backend for tntdb database access library
 This library provides a thin, database independent layer over an SQL
 database.  It lacks complex features like schema queries or wrapper
 classes like active result sets or data bound controls.  Instead you
 get to access the database directly with SQL queries.  The library is
 suited for application programming, not for writing generic database
 handling tools.
 .
 This file has the necessary files for PostgreSQL support.

Package: tntdb-sqlite4v5
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Breaks: libtntdb-sqlite4
Replaces: libtntdb-sqlite4
Description: SQLite backend for tntdb database access library
 This library provides a thin, database independent layer over an SQL
 database.  It lacks complex features like schema queries or wrapper
 classes like active result sets or data bound controls.  Instead you
 get to access the database directly with SQL queries.  The library is
 suited for application programming, not for writing generic database
 handling tools.
 .
 This file has the necessary files for SQLite support.

Package: libtntdb-dev
Architecture: any
Section: libdevel
Depends: libtntdb4v5 (= ${binary:Version}), libcxxtools-dev, ${shlibs:Depends}, ${misc:Depends}, libjs-jquery
Description: Development headers for tntdb
 This library provides a thin, database independent layer over an SQL
 database.  It lacks complex features like schema queries or wrapper
 classes like active result sets or data bound controls.  Instead you
 get to access the database directly with SQL queries.  The library is
 suited for application programming, not for writing generic database
 handling tools.
 .
 Currently has support for MySQL, PostgreSQL and SQLite.