From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: ishi soichi <soichi777@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: local database types for personal use
Date: Mon, 26 Dec 2011 02:37:42 +0100 [thread overview]
Message-ID: <87hb0oi049.fsf@ambire.localdomain> (raw)
In-Reply-To: <CAEjRLuT3E+d0d-jT4HZDOh_EcBcaY9nd_Vg5MvD0iPDa5093BQ@mail.gmail.com> (ishi soichi's message of "Mon, 26 Dec 2011 09:42:08 +0900")
() ishi soichi <soichi777@gmail.com>
() Mon, 26 Dec 2011 09:42:08 +0900
hash-table
assoc
plain text
csv
splite
and maybe others.
Which method would you suggest for developing a local database like this?
If there is just one table in this database, you might try EDB,
whose homepage is <http://www.gnuvola.org/software/edb/>.
next prev parent reply other threads:[~2011-12-26 1:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 0:42 local database types for personal use ishi soichi
2011-12-26 1:37 ` Thien-Thi Nguyen [this message]
2011-12-26 1:47 ` Soichi Ishida
2011-12-26 1:57 ` Thien-Thi Nguyen
2011-12-26 19:08 ` Alan E. Davis
2012-01-22 15:51 ` Alan E. Davis
2012-01-25 6:44 ` ishi soichi
2012-01-22 1:30 ` Samuel Wales
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hb0oi049.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=help-gnu-emacs@gnu.org \
--cc=soichi777@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).