HCMC Blogs

Apparently, my BEFORE INSERT trigger concatenating the owner info with their new id could never have worked (although no bug was ever seen or reported before). What it's trying to do is:

• when a new record is inserted
• concatenate the information about the owner name, address and the record id, and
• store that information in a description field (own_desc) in the record itself.

However, you can run a trigger BEFORE inserting the record (in which case the id is zero, because it hasn't been inserted yet); or you can run it AFTER inserting the record (in which case you cannot update the record itself, because it's already been inserted). The old trigger was doing the former, so the id showed as (0).

So my conclusion is that this either never worked at all, or if it did work, it was a lucky accident that was undone by a regular update to the database libraries, and it won't work in future. Curses.

Received request from IG re photo gallery option.
Have requested IG send me photos (dimensions 158x108) to upload to assets in Cascade.
Currently inquiring about installing/editing photo gallery for IG.

Received request from IG (G&Sl)to investigate number of tweets
showing on right-side.
Page required republishing.
Advised IG.

Reviewing/editing the site:
- updated and styled links
- created new folders on server for audio and video files
- updated specific links re audio and video files
- published pages

Sent website update to BB.

Reviewing/editing the site:
- updated and styled links
- created new folders on server for audio and video files
- updated specific links re audio and video files

Sent website update to BB.

This is part of the cleanup of XML prior to the new site building.

Final corrections to this one.

More tweaks to presentation.

This is quite a brain teaser! I want to go through all the Pandion events to be absolutely certain, but I think that I may be able to solve this problem by making the parentage of Pandion_2 uncertain, and editing their descriptions a bit. I'll update this post as I work on it. I think this reflects what Pausianas is actually saying "there was a Pausanias who was an eponymous hero, but I'm not sure whose son he was."

"The one who was the eponymous hero" is actually an important enough character trait to be unambiguously identified, and so it is worth messing a little bit with the existing Pandions in order to make sure this works.

Update: having looked at this more, I think that Apollodorus' Pandions and Pausanias' Pandions are hopelessly confused. I'm not sure how best to fix this, and am going to put in on the back burner for a while, since I don't think we've confronted exactly this problem before. I think the solution is to decide which aspect of each character is central, and number the characters that way. Then, when authors disagree about events, we'll just create separate bibles with each separate characters. This will create a lot of overlap, but I think it will capture everything most accurately.

I've written custom XSLT to convert the Nanaimo CSV to the CSV for RAD import. At the moment, the actual import fails because of a PHP config issue (we think), but I think the CSV is passable; there are lots of our fields I'm not able to fill, though, and others which are not optimally configured. I'd estimate two hours for this sort of operation on a single spreadsheet, assuming the source repository is not able to generate our own custom spreadsheet.