lnt update is broken because of a missing import and there should be
no need for it anymore, because databases are upgraded when starting
the server. It is not mentioned in the docs.
Details
- Reviewers
MatzeB kristof.beyls cmatthews - Commits
- rL319982: Remove `lnt update` command.
Diff Detail
Event Timeline
I wonder: Is this functionality good for anything nowadays? LNT always performs an upgrade when the server is started, so I don't see why one would want to do it manually. So the better fix may be to just remove the whole function :)
When not removing it, it would be nice to add at least a small sanity test to tests/lnttool.
I used
I just used it to initialize the tables in multiple postgresql databases, as there is no createdb command anymore (I am running a LNT instance with multiple databases). But maybe there is a better way to do that? AFAIK lnt create only initializes a single database, and the empty databases I added additionally where not recognized until I ran lnt update on them.
I would have expected that you can just setup the postgresql connection in lnt.cfg and the tables get created on first server startup. Though admittedly I haven't setup any production servers, so I may be missing something...
Ok I tried it again and indeed the databases are created when starting the server. Should I remove update?