Adam Eisenreich

Please add this to the documentation (in some form): > To run setup locally one can use local installation of Jeager with this command: > `.\jaeger-all-in-one.exe --collector.zipkin.host-port=:9411 --collector.otlp.enabled` I struggled...

Hi, @pantharshit00 would you look into this? This very nasty bug prevents me from using Prisma 4 and above. There is also a problem with introspection (`prisma db pull`), the...

> So the bug should be that uniqueness of fields are guaranteed by @@unique and @@id in any order of the combined fields, not just by the one in use...

I did not think it would change much, but my schema has a small difference; the order of primary index fields. ``` @@id([offerID, carrierID, periodID]) ```

> In which of the models? Both? Just in `nabzak`.

@janpio This is what `db pull` created among many other tables: ```mysql CREATE TABLE `nabzak` ( `idZak` smallint unsigned NOT NULL, `idObdobi` smallint unsigned NOT NULL, `ncis` int NOT NULL,...

@janpio Delete your previous model, it can connect the dots when the `schema.prisma` already existed

Maybe the error got created long, long back, but the VSCode plugin did not recognize it as an error till that point. The last time I checked, the wrong order...

You are using the plugin wrong, you must let it create the type definition file that will fix this error.

I spent at least an hour reading through this (sadly not in order), but at last, I figured out that is going on. Initially, I was happy, that a new...