Drew Jensen wrote:
i, too, have wondered a lot why Postgresql wasn't chosen as the "basic" database. It seems to be so robust, secure, more well-know, is already "network" ready with record-locking, etc. and is OpenSource as well. i don't know that much about dbs but when i tried to find a replacement for MSAc it was the one that "seemed" the best to my very noobie eyes. Oh well...Another old song...ah, and what a great song it was.Over the last few of days I've been helping someone on the OOo users mailing migrate a database from MS Access to Base under Linux. A small business with a deadline to get some work out the door by Monday, who made the mistake of migrating since..well, you know OpenOffice.org has a database now, just like MS.It was quite a trip actually, small detour through Kexi ( seems they can read MS Access under Linux no problem ) - Kexi to Base was a no go also so CSV files and Calc..but in the end he got it done.Then this email pops onto the list just a little while agoSomething strange (but good) happened, which gives me yet one more question. After my last message I went to the store. On the way it dawned on me that I had made a copy of MainBank previously, right in the same database. So when I got home I made a query and, sure enough, the deleted records were still in the copy of MainBank. I was in the process of trying to figure out how to do an APPEND or INSERT INTO when the whole thing seemed to lock up. System Monitor said that soffice.bin was taking 45-50% CPU which, considering that I have a dual core CPU, means that it was sucking up nearly 100% of one of them. So I let it sit for 20 minutes or so, but there was no change, so I killed it. When I relaunched Base it came up with the rcovery window. It successfully recovered the database without incident. However, the queries that I had created were gone. MainBank and its copy were there. So I recreated the queries (copying and pasting your SQL as before). There are three exams, so I created one and then copied and pasted it a couple times to create the other two. And then for the other two I went into the SQL and just changed "LFa" to "LFb" and "LFc." And then I tested each one. Well guess what? All three worked perfectly, including the one whose records had been deleted. I opened MainBank and verified that the records were still there. Yet previously they were definitely gone. Conclusion: Base is not saving changes to a table until some event happens. While it saved me a lot of work this time, this is new to me and I need to understand how Base works here. Previously with Access, and recently with Kexi, when you change a record the change is written to disk the minute you move off the record. Evidently Base doesn't do things that way. At what point does Base write changes to disk? Should I save periodically as I do when working on a Writer document?I do not want to see HSQLdb dumped, I really don't, but I also really don't understand why this situation is considered acceptable.Drewps - You can give the song a listen at http://www.last.fm/music/David+Bromberg/_/Suffer+to+Sing+the+Blues--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Have a great afternoon! :)
smime.p7s
Description: S/MIME Cryptographic Signature
