35 lines
1.0 KiB
Plaintext
35 lines
1.0 KiB
Plaintext
|
Source: pguri
|
||
|
Section: database
|
||
|
Priority: optional
|
||
|
Maintainer: jordi fita mas <jordi@tandem.blog>
|
||
|
Build-Depends:
|
||
|
debhelper-compat (= 13),
|
||
|
postgresql-all (>= 217~),
|
||
|
liburiparser-dev
|
||
|
Standards-Version: 4.6.0
|
||
|
Vcs-Browser: https://github.com/petere/pguri
|
||
|
Vcs-Git: https://github.com/petere/pguri.git
|
||
|
Homepage: https://github.com/petere/pguri
|
||
|
Rules-Requires-Root: no
|
||
|
|
||
|
Package: postgresql-PGVERSION-pguri
|
||
|
Architecture: all
|
||
|
Depends:
|
||
|
${shlibs:Depends},
|
||
|
${misc:Depends},
|
||
|
postgresql-PGVERSION
|
||
|
description: uri type for PostgreSQL
|
||
|
This is an extension for PostgreSQL that provides a uri data type. Advantages
|
||
|
over using plain text for storing URIs include:
|
||
|
.
|
||
|
* URI syntax checking,
|
||
|
* functions for extracting URI components, and
|
||
|
* human-friendly sorting.
|
||
|
.
|
||
|
The actual URI parsing is provided by the uriparser library, which supports
|
||
|
URI syntax as per RFC 3986.
|
||
|
.
|
||
|
Note that this might not be the right data type to use if you want to store
|
||
|
user-provided URI data, such as HTTP referrers, since they might contain
|
||
|
arbitrary junk.
|