A modern programming language that makes developers happier.

kotlinlang

<@U01SP2GJYAU> If I have a postgres view that I generate that doesn't have any id field... is there a way to make an entity for it?

You can use `*@KomapperId(*virtual *=*` *`true)`*  for the entity.

You can also use `@KomapperProjection`.

```@KomapperProjection
data class YourView(
  ...
)```
```val y = ProjectionMeta.YourView
val query = QueryDsl.from(y)```

Even with virtual = true, it still gives me:
```column t0_.id does not exist
io.r2dbc.postgresql.ExceptionFactory$PostgresqlBadGrammarException: [42703] column t0_.id does not exist```
So I guess I'll have to try with a projection... although I didn't know it could be used like that in the querydsl...? If so, that's better...

But now that I think of it... it doesn't really make sense, since a projection by itself wouldn't know which table to query and it seems like an entity requires an id... which I don't have in that view... (well, it's a string... maybe I could use that...?)

&gt; Even with virtual = true, it still gives me:
That error message is not output by Komapper. Is that error related to the entity definition in Komapper?

&gt; a projection by itself wouldn’t know which table to query
Try following code:
```@KomapperProjection
@KomapperTable("EmployeeView")
data class YourView(
  ...
)```
```val y = ProjectionMeta.YourView
val query = QueryDsl.from(y)```

&gt; That error message is not output by Komapper. Is that error related to the entity definition in Komapper?
That field really doesn't exist on the table... but I thought that a Komapper Entity w/o an id field (which I don't have in this case...) won't work? So I added the field and thought that virtual would make it that Komapper doesn't look for it at all in a query.

Do not add fields that do not exist in the View; give `@KomapperId (virtual = true)` to fields that exist in the View and are substantially unique.