Specialized, Open Source Databases?

PyTHON71 asks: "I've been asked the head of the Wichita State University Anthropology department to help fix his growing biological anthropology collection database. It's currently in Access (insert boo's and hisses), but he is willing to have it developed in a reliable open source format. Now, there are a lot of university departments out there that need to have specialized work done on a small budget. They can't rely on just any developer, because the developer has to know biological anthropology (in this case) as well as MySQL, etc. And since it's not in the Hacker Code to duplicate work that's already been done, I was wondering what specialized database projects are out there & available for general use (not the data, just the structure)."

Comments

Why?

[LordNimon]

Why does the developer have to know biological anthropology? Can't the developer just work with the scientists to understand the data formats, and create the database for them, and then teach them how to use it?

Re:Why?

[AndyElf]

I guess his question is mis-phrased: he wants a ready application/database for that very purpose that is not proprietary.

What about Access?

[GTRacer]

While I don't have a great love of the "Evil Empire" that is MS, what's so bad about Access? It's certainly not perfect, but tell me what Windows-based alternatives exist that will:

* Let me create front-end forms populated and controlled by code and query

* Support relational tables, indexes, complex JOIN queries, aggregate functions, etc.

* Design complex reports with page/section formatting and behind-the-scenes code controls

* Can access ODBC data sources

If you can show me the way, I'll take the first step! I'd love to cut some of the distribution costs here!

GTRacer
- Needs help with gcc + PS2...

Re:What about Access?

[SLiK812]

The problem is Access's data storage is in a flat file format. Which means it'll be slower than dookie after it gets to be a certain size and complexity. Especially when sharing the database with many users. I'd suggest SQL Server, with a vb frontend or even an Access frontend with the SQL Server tables linked into Access.

Unfortunately the question was pertaining to open source, probably because the owner of the data, doesn't want to drop a chunk of change on a major database. Yes Access comes with Windows, but the performance issue is too big.

Re:What about Access?

[Anonymous Coward]

Most of the time, whenever anyone posts about database, I like to point out Adaptive Server Anywhere (from Sybase). It's ....

- inexpensive

- probably the easiest DB to administer

- fully SQL compliant, supports ESQL/C, ODBC, OLEDB, JDBC

- available in linux, windows, mac, aix, etc. versions

- available for free download (as an evaluation copy) off the sybase website

- advanced query optimizer (blows most open source engines out of the water .... really)

- fully ANSI transaction-oriented; stable in the event of disaster (which is really what you pay for when you buy a database)

- comes with all sorts of other goodies in the suite (lets you make forms like Access [via "Infomaker"], database/UML graphs, etc) -- mostly things i don't use, but probably some things that an Access user would like

- can run on anything from mainframes to palm pilots (ASA has technology that lets it generate specialized database engines that run on handhelds in as little as 80kB)

start your first step here:

http://www.sybase.com

Re:What about Access?

[metacosm]

I am not sure about the data storage of access. It was my understanding it was NOT a flat file -- but it is very limitted.

I recommend you use the "upsize" wizard (which will automatically relink to your existing forms) and goto MS SQL 2000.

This does a few things for you. #1. Huge number of people familar with Access. (Better chance of finding a "biological anthropology" major with experience [I should note, I find this requirement a bit silly, have a guy from the CS department set it up, and you use it]). #2. The app appears to work exactly like it did -- only without the preformance hangups.

Once you get thru that basic change -- and you have de-coupled the interface (access) from the backend (sql server 2000) -- you can slowly but surely start fixing the design of the database without interupting the USAGE of the system too much. The forms will be consistant, and you just have to ensure that you keep them up to date with the database changes you make.

I hate to be putting forth an MS solution on /. -- but I think it is probably the most sane answer. :)

database?

[Kevin Stevens]

Why dont you explain what you mean by 'database' first. A database can mean different things. I am not sure if you want a complete database application, front end and all, or if you just want a database design- A UML model or E-R diagram, from which SQL DDL can be created. (or perhaps by open source you meant SQL code to Create a database). Your requirements are kind of blurry to me. Doing something like this should not really be all that difficult though. If you have a developer look at the kinds of data you are trying to store, and the relationships between those data (in depth knowledge is not required of what the data actually means, though I guess it helps) a developer should be able to come up with a Data model and front end relatively easy.

Do you really have to have this answered?

[dacarr]

Asking for this beast is like asking for a version of M$ Excel (or, to be fair, Gnumeric) that is specifically designed toward balancing a company's books.

A database is a database. There is no "specialized" database for any purpose, with the possible exception of design for platform (IE, DB/2 for AS400) - you build the structures in the DB program and go. It's what makes apps and engines like MySQL really cool.

If you want a DB that is geared for bio-anthropology, fire up MySQL or PostGreSQL or insert your favorite engine here, build the structure for the DB you need to run, put a pretty face on it for the users, and kick back as it does the rest.

Maybe I'm missing something

[fean]

Here's what I understand:
you already have everything up and running on an access database
you want to use a different database platform

doesn't sound like you need to worry about designing anything, its already there.... especially if you want to go from access to MySQL (or any other of the same family), just build the database structure to match the old one, export to .csv from word, and import to your chosen database... interfacing should be similar, it depends on how you're accessing it (if web based, and you have admin privs on the host machine, you just change the database type in the control panel, google:asp+mysql )...

so unless I've over simplified something, sounds like this is a classic mountain != molehill problem

SQLITE

[ddriver]

It supports almost all sql92, is blazingly fast, it has an ODBC interface and native api's for c and c++, is has a python db api 2.0 compliant interface. It has a really cool and versatile command line tool. It is imbedded though, so if you want to you it as a server you will want to write the implementation. I don't think that it would be too hard though, depending on what you wanted to do with it. I have just started a payables application withit and it looks like it will work out quite well.

Oh, and it is public domain.

Re:SQLITE

[ddriver]

try www.sqlite.org

Here is the licensing terms from source: /*
** 2001 September 15
**
** The author disclaims copyright to this source code. In place of
** a legal notice, here is a blessing:
**
** May you do good and not evil.
** May you find forgiveness for yourself and forgive others.
** May you share freely, never taking more than you give.
**

Dude I so dig that!