Elle Mouton a291d6f1a6 graph/db+sqldb: improve efficiency of node migration ...

There is no need to use the "collect-then-update" pattern for node
insertion during the SQL migration since if we do have any previously
persisted data for the node and happen to re-run the insertion for that
node, the data will be exactly the same. So we can make use of "On
conflict, no nothing" here too.

2025-09-01 08:02:38 +02:00

..

db

graph/db+sqldb: improve efficiency of node migration

2025-09-01 08:02:38 +02:00

testdata

refactor: move various duties from ChannelRouter to graph.Builder

2024-07-15 15:56:33 +02:00

builder_test.go

refactor+multi: use *lnwire.FeatureVector for ChannelEdgeInfo features

2025-07-01 17:02:07 +02:00

builder.go

graph: remove outdated TODO

2025-08-13 08:45:52 +02:00

errors.go

multi: use the "errors" package everywhere

2025-06-30 09:46:55 +02:00

interfaces.go

multi: let ForEachNodeChannel take a reset param

2025-07-15 11:23:27 +02:00

log.go

multi: start updating various loggers to use the new v2 type

2024-10-22 17:03:55 +02:00

notifications_test.go

refactor+multi: use *lnwire.FeatureVector for ChannelEdgeInfo features

2025-07-01 17:02:07 +02:00

setup_test.go

refactor: move various duties from ChannelRouter to graph.Builder

2024-07-15 15:56:33 +02:00

stats.go

graph: rename routerStats to builderStats

2025-02-07 13:01:39 +02:00