mySQL DB not working

cepheid · 10-07-2010, 04:01 AM

I've got v6.4.1 installed, and am trying to use the mySQL database. It's not working. EPC is able to login to the mySQL server just fine - the setup.php script was able to create the epc_calendar table in the DB. However, when I try to add a new event, the event never gets added... EPC tells me that the event was added to the DB, but the event does not appear in the calendar display and no rows are actually added to the table (I checked with phpMyAdmin).

The flatfile database works just fine.

And, there's a probably-related bug: if I turn off the flatfile DB but do not erase the flatfile DB filename, any events I try to add to the mySQL DB get added to the flatfile DB instead, even though I disabled the DB... but, the flatfile DB contains only the last event entered. In other words, if the flatfile DB is disabled, any attempt to write an event to the mySQL DB fails on the mySQL DB and erases the flatfile DB, then writes that event to the flatfile.

If the flatfile DB is disabled, EPC shouldn't be touching it at all... it should especially not erase it! I was stupid and failed to back up my flatfile DB, and ended up losing the whole thing because of this bug.

1) Why is EPC failing to write events to the mySQL database, but not giving me any errors?
2) Why is the flatfile DB still being accessed for writing events (and why is it being erased) when flatfiles are disabled?

Please help ASAP.

EPC v6.4.1, php v5.1.6, mySQL v5.0.77 on CentOS 5.4

**Brian** · 10-07-2010, 12:09 PM

Please open a support ticket with your calendar URL and login.

cepheid · 10-07-2010, 05:41 PM

I figured out what leads up to the problem... EPC is confused if trying to use BOTH mySQL and flatfile DB formats at the same time. If I enable both mySQL and flatfile, then EPC will display events from both sources. However, any new events end up only in the mySQL database, not in the flatfile.

However, the problem happens when trying to edit an event that is in the flatfile DB... EPC says "Switching to flat-file database mode," and that's when things start to get weird. After getting that message, any new events end up only in the flatfile DB, not in the mySQL DB - this is an interface inconsistency and shouldn't happen. This then leads to the next problem: if I then disable the flatfile DB, EPC gets really confused... it tries to write to the flatfile, not to the mySQL DB, but it writes only a single event because the flatfile DB is disabled.

If I log out of EPC (to clear all the cookies) and log back in, EPC begins to behave "properly" again. It appears that this is basically an in-session issue, caused by EPC remaining in "flat-file mode" after editing a flatfile event, instead of reverting back to mySQL mode as it should.

So... I suspect this whole issue stems from a bug in trying to simultaneously handle both mySQL and flatfile DB modes. There is good reason to be using both modes, however: for example, lots of legacy events in a flatfile mode but wanting to switch (for current/future edits) to mySQL.

If we are not intended to use both mySQL and flatfile at the same time, then EPC should disallow this option - enabling one should disable the other, and there should be documentation to that effect. If we are allowed to use both at the same time, then whatever is causing this bug should be fixed... for example, after editing the flatfile event, EPC should switch back to mySQL mode so that it's not trying to edit the flatfile anymore, i.e. EPC touches the flatfile only when it needs to (when editing an event that's in the flatfile), but otherwise is in mySQL mode.

I've opened a support ticket for this (XAD-728636), but I'm pretty sure this is now a real bug, not a support issue.

Let me know if I can be of more assistance.
Thanks.

**Brian** · 10-07-2010, 10:14 PM

The calendar will use the database that was selected when logged into the calendar. If you have both selected, mySQL takes precedence after the next login.

cepheid · 10-07-2010, 11:05 PM

Under normal circumstances, yes. However, if both methods are selected (i.e. mySQL takes precedence) and you edit an event in the flatfile, the calendar switches to use the flat-file mode... any new events added to the calendar during that same session will only be added to the flatfile. If you follow the sequence of steps I outlined in the support ticket, you'll see what I mean.

I realize v7 will use mySQL only, but in the meantime, I strongly recommend fixing this bug for v6.4.2, since although probably not common, it could still bite anyone.

Thanks.

ve9gra · 10-09-2010, 01:43 AM

In order to minimize issues, I do offer the free service of converting your flat-file db into a .sql script that you can simply import into your mySQL table so that you are then using a single db mode.

cepheid · 10-09-2010, 02:16 AM

Gervais: thanks, I may take you up on the offer, though v7 will also include a converter, so I might just wait for that. In the meantime, I'll just pick one method and use it... most likely the flatfile method since I already have a few dozen events stored. I'll definitely keep it in mind, though, thanks.