using oobase as stand-alone database vs as front-end to mysql or postgresql
I need to create a database for a small business. It won't be very big but there will be lots of one-to-many relationships between the tables. The business is aiming to expand - at the moment allowing multiple users and remote access would be useful but not necessary, but eventually (hopefully) it is going to be essential.
They want to be able to start using the database asap, with a nice simple user interface. I'm starting from absolute scratch...
As far as understanding the structure of the database goes, and creating it in sql, I don't have any problems at all. I'm working on the basis of using oobase initially as the front-end interface - possibly moving to a more tailored solution using php or whatever when I've learnt how to use them.
The eventual requirements for multiple user and remote access made me assume that mysql or postgresql would be the appropriate applications to use. However, I'm having problems trying to understand and configure all the server stuff (user access, host names, security) -it's all totally new to me.
There's also the added complication that they don't have a separate server computer - one of the desktop computers doubles as the server. They know they need to get a proper server at some point, but... If they get a big contract which requires lots of working away from the office they will sort this out quickly, otherwise it could be a year or more down the line...
I know in theory I could start just using oobase then move the data across to a full database server later - is this a practical solution or more problematic than it's worth? And would moving/reconfiguring mysql or postgresql be even worse??
Many thanks in advance for your help,
I got used to using postgresql, it used to be difficult to setup.
Which distro are you using ?
Debian sets up postgres to a usable default on install, you then have a fair amount of reading and learning.
What doesn't kill you makes you stronger.
But I am inherently lazy, I now mainly use sqlite which also interfaces with openoffice.
How large is the company, how large or complex could the database become, check benchmarks, will a smaller db give you what you need simpler, will your i/f language give you the required security.
I would suggest do it once, do it right, don't change horses mid-stream, you're only doubling your work load.
If you go with mysql, I've found the mysql-administrator program makes adding and configuring user permissions a snap.
If you would like to brush up on the sql language, the book "MySQL Crash Course" by Ben Forta is excellent.
OO is quite usable if you want to learn it. It is similar to many databases.
They kind of have the documentation all over the place for most of OO. See this. http://wiki.services.openoffice.org/wiki/Database
I agree, if you're going to need eg MySQL, go with it upfront. Saves learning 2 systems.
You can still use OOBase as a front-end if it makes sense.
The (very good) MySQL docs & forums are here http://dev.mysql.com/doc/refman/5.0/en .
For an admin front-end, you can also look at phpMyAdmin http://www.phpmyadmin.net/home_page/index.php and see which one you prefer. It should be in your repos I believe.
Can't really get much more specific until you decide which DB to use.
Do keep a copy of the DB on another system eg at home if that's allowed. This is for recovery purposes and research.
Many thanks for your replies - coming to the conclusion that I need to learn about sorting the network anyway, so then the setting up different types of access will make sense! From your replies it's sounding like moving the server to new hardware as and when that happens shouldn't be too difficult once I've worked out how this network connects to each other...
So now I have a big stack of books about networking from the library to wade through!
|All times are GMT -5. The time now is 02:16 PM.|