RE: RE: RE: RE: Community Teaching Project

Well, the problem here is also the target market. If we're working on this as a small desktop app, then a significant portion of the users aren't going to have a database installed, regardless of whether they're a Windows user or *nix user.

The best option might be two separate versions; one that's DB driven, and select a "required" DB like MySQL, and one that's CSV driven. The CSV version would satisfy the cross-platform requirement (done properly) while the MySQL version offers higher performance.

As for project management and communication - we're working on that one.

- Ozymandias

Comment on RE: RE: RE: RE: Community Teaching Project

Replies are listed 'Best First'.
RE:(5) Community Teaching Project by swiftone (Curate) on Jun 16, 2000 at 18:23 UTC
The best option might be two separate versions; one that's DB driven, and select a "required" DB like MySQL, and one that's CSV driven. The CSV version would satisfy the cross-platform requirement (done properly) while the MySQL version offers higher performance. I believe there is a DBD::CSV that would allow us to design with a database interface, and have the option of pointing that interface at a CSV file if needed.	[reply]

Replies are listed 'Best First'.

RE:(5) Community Teaching Project
by swiftone (Curate) on Jun 16, 2000 at 18:23 UTC

I believe there is a DBD::CSV that would allow us to design with a database interface, and have the option of pointing that interface at a CSV file if needed.

[reply]