aboutsummaryrefslogtreecommitdiff
path: root/databases/Makefile
diff options
context:
space:
mode:
authorMichael Johnson <ahze@FreeBSD.org>2005-11-06 01:47:33 +0000
committerMichael Johnson <ahze@FreeBSD.org>2005-11-06 01:47:33 +0000
commit946593c1f35e848b31d8197c6dc7396820cf392d (patch)
tree83111e07ac62397d0537428f95ac945f6a9fd8eb /databases/Makefile
parentb380d46ac278bc111746fb271cc17d4b0dffb94e (diff)
downloadports-946593c1f35e848b31d8197c6dc7396820cf392d.tar.gz
ports-946593c1f35e848b31d8197c6dc7396820cf392d.zip
- Add glom
With Glom you can design table definitions and the relationships between them, plus arrange the fields on the screen. You can edit and search the data in those tables, and specify field values in terms of other fields. It's as easy as it should be. The design is loosely based on FileMaker Pro, with the added advantage of separation between interface and data. Its simple framework should be enough to implement most database applications. Without Glom these systems normally consist of lots of repetitive, unmaintainable code. Glom-specific data such as the relationship definitions is saved in the Glom document. Glom re-connects to the database server when it loads a previous Glom document. The document is in XML format. Glom uses the PostgreSQL database backend but it can not edit databases that it did not create, because it uses only a simple subset of Postgres functionality. Submitted by: adamw
Notes
Notes: svn path=/head/; revision=147423
Diffstat (limited to 'databases/Makefile')
-rw-r--r--databases/Makefile1
1 files changed, 1 insertions, 0 deletions
diff --git a/databases/Makefile b/databases/Makefile
index 02dac87b2f4d..070838ef5f18 100644
--- a/databases/Makefile
+++ b/databases/Makefile
@@ -55,6 +55,7 @@
SUBDIR += gbib
SUBDIR += gdbm
SUBDIR += gigabase
+ SUBDIR += glom
SUBDIR += gmysql
SUBDIR += gnats
SUBDIR += gnats4