MySQL or LDAP? and MySQL or ProtegeSQL?

Anon

MySQL or LDAP: I'm making a website to manage a small group and I was planning on using MySQL to handle all the MemberInfo. Yet, someone else is really pushing to use LDAP to handle the MemberInfo. This DB within the next 4 years will probably not contain more than 1600 members. Actually thats if we include inactive members. At once if we only include active members we'd only have 100 or so people in this DB. Is LDAP really gonna make that much of a diff? So far I don't think so. Any one have any thoughts?

MySQL or ProtegeSQL: Same site, i've read the benchmarks and everything. The thing is that this site probably won't be big enough to see the preformance difference of either of the two flavors. News content, pics, and maybe a few other tables. But thats about it. I don't think it makes a difference either way (i'm going with MySQL as of now) but if anyone has any thoughts on the contrary, i'd like to hear them.

Anon

One important point to consider is to analyze how the database will be used.
LDAP is specifically tuned for searches rather than updates (add/modify/delete).

So if lot of updates (and transactions) are expected, then RDBMS is the way to go. But if search is primary (I remember statistics like, LDAP is very efficient if you do one or two updates per 100 searches), then
LDAP is the way to go.

Regarding APIs and ease of use and cost,
LDAP/mysql/postgresql, there is no big difference.

Hope that helps.

-k