[PATCH] D40704: Import db.migrate module in update command.

Matthias Braun via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Fri Dec 1 11:00:22 PST 2017


MatzeB added a comment.

In https://reviews.llvm.org/D40704#942454, @fhahn wrote:

> I used
>
> In https://reviews.llvm.org/D40704#942439, @MatzeB wrote:
>
> > 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 :)
>
>
> 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...


https://reviews.llvm.org/D40704





More information about the llvm-commits mailing list