K
Kysely•2mo ago
tzezar

Query result type mismatch

For unknown to me reason kysely adds categoryId to nested object built with jsonObjectFrom or maybe it does not take related table, but copies selectFrom table. Why does it happen? https://kyse.link/0sjoX 
export interface Product {
  categoryId: number;
  description: string;
  id: Generated<number>;
  name: string;
}

export interface ProductCategory {
  description: string;
  id: Generated<number>;
  name: string;
}
export interface Product {
  categoryId: number;
  description: string;
  id: Generated<number>;
  name: string;
}

export interface ProductCategory {
  description: string;
  id: Generated<number>;
  name: string;
}
That type is different compared to my database state and generated interfaces with kysely-codegen 
const dbProducts: {
    id: number;
    name: string;
    description: string;
    categoryId: number;
    category: {
        id: number;
        name: string;
        description: string;
        categoryId: number;
    };
}[]
const dbProducts: {
    id: number;
    name: string;
    description: string;
    categoryId: number;
    category: {
        id: number;
        name: string;
        description: string;
        categoryId: number;
    };
}[]
it should be: 
const dbProducts: {
    id: number;
    name: string;
    description: string;
    categoryId: number;
    category: {
        id: number;
        name: string;
        description: string;
    };
}[]
const dbProducts: {
    id: number;
    name: string;
    description: string;
    categoryId: number;
    category: {
        id: number;
        name: string;
        description: string;
    };
}[]
No description
Solution:
Use selectAll('product_category') instead of selectAll() in the subquery
Jump to solution
3 Replies
Solution
koskimas
koskimas•2mo ago
Use selectAll('product_category') instead of selectAll() in the subquery
koskimas
koskimas•2mo ago
https://kyse.link/Z1ZBq I implemented selectAll that way because I think some dialects actually select the parent columns as well if you use *. But I might've been wrong about that and it's actually just implemented wrong. But It's better to use table.* than * anyway. It's more specific and often makes the query easier to read.
tzezar
tzezarOP•2mo ago
Got it! That makes sense now. Thanks for the clarification! Using table.* does seem like a better approach for readability and consistency. Appreciate the help! 🙌

Did you find this page helpful?