Comment 3 for bug 1754298

I can replicate this problem and your fix works fine, but it's doing a bit more work than it actually needs to. I'm going to commit a streamlined (and cleaned up) version of dbCreateAlias() to the 3.15 branch and merge it up (there were other changes to it between 3.14 and 3.15 that I just decided I don't want to deal with).

Note that the dbStaticTest.db file only exists on the 3.16 branch, and I don't want to add it during the merge up from 3.15, so the automated test will only appear when we merge your info_fields branch. My changes to dbCreateAlias() will conflict with yours in that branch, but I will correct that during the merge (the Merge Request will probably start to show a conflict, which you can ignore).

I wonder if we'll ever find a use for creating an info field on an alias? With this fix there shouldn't be any way to create one from a .db file, but it will still be possible.