Multiple databases feature repository can not be provided

I’m submitting a…

[ ] Regression 
[*] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

New Error in 6.1.0 (6.0.0 is ok)

const defaultOptions = {
  type: 'postgres',
  port: 5432,
  username: 'user',
  password: 'password',
  database: 'db',
  synchronize: true,
};

@Module({
  imports: [
    TypeOrmModule.forRoot({
      ...defaultOptions,
      host: 'photo_db_host',
      entities: [Photo],
    }),
    TypeOrmModule.forRoot({
      ...defaultOptions,
      name: 'personsConnection',
      host: 'person_db_host',
      entities: [Person],
    }),
    TypeOrmModule.forRoot({
      ...defaultOptions,
      name: 'albumsConnection',
      host: 'album_db_host',
      entities: [Album],
    }),
  ],
})
export class ApplicationModule {}

@Module({
  imports: [
    TypeOrmModule.forFeature([Photo]),
    TypeOrmModule.forFeature([Person], 'personsConnection'),
  ],
  providers: [
    PhotoService,
    PersonService
  ]
})
export class SubModule {}

@Injectable()
export class PersonService {
  constructor(
    @InjectRepository(Person) private readonly repo: Repository<Person>,
  ) {}
}

@Injectable()
export class PhotoService {
  constructor(
    @InjectRepository(Photo) private readonly repo: Repository<Photo>,
  ) {}
}

Get error Nest can't resolve dependencies of the PersonService (?). Please make sure that the argument at index [0] is available in the SubModule context.

Environment

Nest version: 6.1.0

 

[kamilmysliwiec]

Why add this constraint in 6.1, when it did not exist in 6.0 ?

It was a bug. Previously, if you registered 1 entity under 2 connections at the same time, you wouldn’t be able to inject the second one (they would override each other). @InjectRepository() uses default connection, unless you specify the connection name as a second parameter. In order to explicitly set the connection name, use construction that I’ve set out above:

@InjectRepository(Person, 'personsConnection') 
private readonly repo: Repository<Person>,

We’ll update the docs for better clarity. I’m sorry for your inconveniences.

[kamilmysliwiec]

@Napas It’s not a connection detail but rather a token, indicator for which connection you want to use (if you have multiple of them) - which is totally fine.