Currently, ircloggr interpolates strings into the database -- with mild massaging -- to create a table for each channel. This is pretty bogus. Some day, someone will extend ircloggr to have user-configurable channels that it lurks on, and will get owned six ways to Sunday.
This needs to be documented, or preferably, fixed. (The fix is to keep everything in one table with an added column for 'channelid', and have another table with a {channelid, server, channel}.)
33 is a workaround for one particular failure mode that bit me this evening, but there are many more...
Currently, ircloggr interpolates strings into the database -- with mild massaging -- to create a table for each channel. This is pretty bogus. Some day, someone will extend ircloggr to have user-configurable channels that it lurks on, and will get owned six ways to Sunday.
This needs to be documented, or preferably, fixed. (The fix is to keep everything in one table with an added column for 'channelid', and have another table with a {channelid, server, channel}.)
33 is a workaround for one particular failure mode that bit me this evening, but there are many more...