On October 28, [EMAIL PROTECTED] said:
>
> Any thoughts? If this isn't appropriate discussion here, let me know.
My stand on this would be no, no, no. Really. No. BBDB works quite
nicely, with vast quantities of entries, using a flat file. The file
is read using native emacsisms (there's some d
Today, Benjamin Rutt <[EMAIL PROTECTED]> wrote:
> Modifying db schema is not trivial or elegant with any RDBMS that I've
> ever heard of. Besides, adding a new field on the fly is easy with
> the current bbdb implementation. Doing it with a RDBMS would be quite
> difficult, and many RDBMS imple
Andreas Fuchs <[EMAIL PROTECTED]> writes:
> On 2000-10-28, Tom Perrine <[EMAIL PROTECTED]> wrote:
> > If someone were to build such a PIB API, it seems that the hardest
> > part would be to support the current "invent a new field on the fly"
> > features.
>
> Nah, not at all. You could have a ta
Today, I <[EMAIL PROTECTED]> wrote:
> Hm. If I find time today, I'll try to hack together a little ERD in dia
> so you can see what I'm talking about.
Done. You can look at it at
http://www.htlwrn.ac.at/d96001/bbdb/bbdb-er.html>.
Have Fun,
--
Andreas Fuchs, <[EMAIL PROTECTED]>, <[EMAIL PROTECT
> "KG" == Kai Großjohann <[EMAIL PROTECTED]> writes:
KG> 2.2 will help with syncing with a Palm, and all my colleages (and
KG> I) have one, now.
> "JK" == Jochen Küpper <[EMAIL PROTECTED]> writes:
JK> Dunno, sorry.
JK> I can heartly suggest upgrading to the current head of cvs. See
JK
On 2000-10-28, Tom Perrine <[EMAIL PROTECTED]> wrote:
> If someone were to build such a PIB API, it seems that the hardest
> part would be to support the current "invent a new field on the fly"
> features.
Nah, not at all. You could have a table that contains all notes field
names (and an ID), a
