LR2: non-official SQLite fix for non-exporting keywords

Question

Hello
This is not the official Adobe fix.
I've been looking into this and it's relatively trivial to update the catalog using SQLite tools to update a catalog so that keywords are exported again.
Please note that you do this at your own risk.
-- Start --
1. Obtain an SQLite tool - I use SQLiteSpy, there are others for both Windows and Mac - search this forum for examples.
2. Close Lightroom if it is running.
3. Backup your .lrcat file
4. Start your SQLite tool, and open your .lrcat file.
5. Execute this query:
update aglibrarykeyword
set includeOnExport = 1, includeParents = 1, includeSynonyms = 1
where parent is not null
6. Close your SQLite tool
-- End --
This will set all three options on your keywords, and should make any keyworded image export with the keywords. However, this fix sets all three options on all your keywords, it doesn't match the options you had in LR 1.4.1. If you're not confident with running these steps, I suggest you wait for an official fix.
Zak

Answer 1

I've been experimenting with this, taking advantage of what Zak already described.
But Im finding that some of the keywords *are* written out. And by using SQLiteSpy to looking into my 1.X and 2.0 catalogs its pretty easy to see where they botched up the conversion.
I think the problem is something like this...
For each keyword, if you have never fiddled with the Keyword Tag Options for a keyword then the 1.X catalog has the corresponding values in the set to NULL (the three properties are actually stored as a string containing Lua code to create a table with these three values). If you fiddle with any of them then they get set (all of them). The 2.0 conversion process seems to do the right thing when converting non-NULL values. Its when the 1X database has a NULL that they screw up, putting a false in the 2X database, when they probably should have inserted true instead.
Ive now got a swag at fixing this, but I cheated. I run an UPDATE statement on the 1.X catalogit will supply true values for all three settings on keywords that currently have no value. You then need to run LR 2 to convert the catalog to the new format, and things seem to work ok.
Heres the query. Remember this is to be run on the 1.X catalog. Specifically, I was using Lr 1.4.1, and havent tried with earlier versions. And all normal warnings about making backups, not trusting code you find on forums, etc, apply.
update AgLibraryTag set flattenedParams = "params = { includeOnExport = true, includeParents = true, includeSynonyms = true, }" where flattenedParams is NULL;