Prisma - No destination for column XXXXX #12
-
|
Hi, Just started using Bob as a replacement to the now unmaintained prisma go lib. Got my files successfully generated from the schema.prisma file, but running into an error I can't figure out. Sample prisma schema: Code:
Any pointers to where I've gone wrong here? Cheers |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
I was unable to replicate this. Did you make sure that your database is up to date by running your migrations? I tried with this schema: generator db {
provider = "go run -mod=mod github.com/stephenafamo/bob/gen/bobgen-prisma"
output = env("PRISMA_OUTPUT")
}
datasource db {
provider = "sqlite"
url = "file:demo.db"
}
model Business {
id Int @id @default(autoincrement())
name String
description String
slug String @unique
owner User @relation(fields: [ownerId], references: [id])
ownerId Int
setup Boolean @default(false)
}
model User {
id Int @id @default(autoincrement())
createdAt DateTime @default(now())
updatedAt DateTime @updatedAt
businesses Business[]
}After running the migrations with package main
import (
"context"
"fmt"
"playground/prisma/"
"playground/prisma/factory"
"github.com/stephenafamo/bob"
)
func main() {
if err := run(context.Background()); err != nil {
panic(err)
}
}
func run(ctx context.Context) error {
client, err := prisma.New()
if err != nil {
return err
}
defer client.Close()
db := bob.DebugExecutor(client, nil)
_, err = factory.New().NewBusiness().Create(ctx, db)
if err != nil {
return err
}
businesses, err := prisma.Businesses(ctx, db).All()
if err != nil {
return err
}
fmt.Printf("%#v\n", businesses[0])
return nil
}And this was the output: |
Beta Was this translation helpful? Give feedback.
-
|
Apologies for the delay here @stephenafamo - I can confirm this works with the schema you provided in your example. I attempted to trim down the schema to provide a concise example here, but seemingly that made it work 😅 Here's the full schema that I've verified I'm getting an issue with: https://gist.github.com/tombowditch/45bf4e9c424cdbc24a41ad91e8226cb7 Using your example (with the Am I being dumb somewhere here? 😅 |
Beta Was this translation helpful? Give feedback.
-
|
Not your fault at all 😔. There was a clash in the autogenerated factory types. I've pushed a change to make these clashes a lot less likely. Try with the current master: go get github.com/stephenafamo/bob@b29e53b |
Beta Was this translation helpful? Give feedback.
-
|
That works, |
Beta Was this translation helpful? Give feedback.
-
|
OK @stephenafamo - that fixed the second error I was getting with running the app, however I am still getting the prisma schema: https://gist.github.com/tombowditch/45bf4e9c424cdbc24a41ad91e8226cb7 client, err := prisma.New()
if err != nil {
return
}
defer client.Close()
db := bob.DebugExecutor(client, nil)
businesses, err := prisma.Businesses(ctx, db).All()
if err != nil {
fmt.Println(err) # logs out "No destination for column ownerId"
return
}Any idea on this one? Apologies :) |
Beta Was this translation helpful? Give feedback.
-
|
Works for me. I had to add some factory mods since Bob will not automatically set However, it works as expected. package main
import (
"context"
"fmt"
"playground/prisma"
"playground/prisma/factory"
"github.com/gofrs/uuid"
"github.com/stephenafamo/bob"
)
var f = factory.New()
func init() {
f.AddBaseUserMod(factory.UserMods.IDFunc(func() string {
return uuid.Must(uuid.NewV4()).String()
}))
f.AddBaseBusinessMod(factory.BusinessMods.IDFunc(func() string {
return uuid.Must(uuid.NewV4()).String()
}))
}
func main() {
if err := run(context.Background()); err != nil {
panic(err)
}
}
func run(ctx context.Context) error {
client, err := prisma.New()
if err != nil {
return err
}
defer client.Close()
db := bob.DebugExecutor(client, nil)
_, err = f.NewBusiness().Create(ctx, db)
if err != nil {
return err
}
businesses, err := prisma.Businesses(ctx, db).All()
if err != nil {
return err
}
fmt.Printf("%#v\n", businesses[0])
return nil
}Logs: |
Beta Was this translation helpful? Give feedback.
I was unable to replicate this. Did you make sure that your database is up to date by running your migrations?
I tried with this schema: