Where is Base?

users
#21

I have not kept up with Base, I tend to use MariaDB/PostgreSQL directly;
not through the Base front end. I vaguely remember some chatter about
replacing HSQL with something else.

#22

Replacing an excellent database engine with another excellent database
engine will not solve any problem because HSQL is _not_ the problem.

#23

You have described my situation exactly. I use Base once a year, to print out address labels for Christmas cards. I keep the address list in a spreadsheet and link to Writer through Base. It took me forever to learn how to do it, but now that I know, it works great.

Virgil

#24

Hi :slight_smile:
The way Andreas describes Base's internal back-end makes a lot of sense out
of what i have always heard about the internal back-end functioning so
badly. Trying to read/write into a file inside a zip-file is often tricky
and i just hadn't thought about that wrt Base.

However, i was under the impression that the devs move to using a different
internal back-end would give them a chance to do a better job of it.
Sometimes prototyping really helps identify difficult areas. Also running
a system for a long time does sometimes flag up issues that may not have
been noticeable at the time.

So i thought the move to a different internal back-end would at least make
it possible to upgrade that back-end and maybe keep it less heavily tweaked
and thus more inline with their own documentation to help people with all
sorts of issues. Even just a couple of things like that might be a huge
improvement.
Regards from
Tom :slight_smile:

#25

I have read with interest the emails on Base. I have always regarded the data base component of Open Office, Libre office as the equivalent to the datbase component of MS Access. I have 5 data bases, originally run under windows and MS Access which I have converted to run under Libre Base. I have found the LibreBase is probable slightly easier to use than MS Access and it certainly copes very well with my data bases, all of which are small. (The biggest has about 5000 records) The only problem I have had is in a new database where I needed to store photos against each record. It quickly gave up after about 4 records. I am not certain why, but other claims on my time have prevented me for investigating what caused the problem.

I was a database administrator for many years with extremely large data bases (millioms of records) using Oracle, etc. When I needed to manage a large data base (about 100,000 records, 30 to 40 users) in linux, I used MySQL with web based front end using PHP to connect to the database.

My advice to people needing to use databases is to use Base for small databases (less than 10000 records). For larger bases consider using Mysql with a web based front end and PHP to connect to the databse.

Regards

Peter Goggin

#26

Hi Peter

Noted on your comments and others....

I can confirm that using the embedded DB in Base is a disaster - I battled with it for a couple of years until I found out about using an external engine - I use MySQL and have had _NO_ problems, (except my own finger problems!!) since then.

Regarding images in the Database I have about 2600 records with a maximum of 7 images per record. I had no problems with this under Base/MySQL except that the DB file gets very large as a copy of each image is included in the DB. I just recently came across a tutorial on 'Linking Images' rather than including them and this works like a charm and the DB stays much smaller and therefore faster.

The tutotial can be found here -/_www.youtube.com/watch?v=IsHqqvn2zYg_/ <https://www.youtube.com/watch?v=IsHqqvn2zYg>

Another nice plus is that if you control your image file names you can be sure that your DB always shows the latest image - works for me!!

Hope this helps

IanW
Pretoria RSA.