Error: VT12001: unsupported: JOIN between derived tables about jackson HOT 8 CLOSED

Closing this issue for now since the solution above worked! Will let you guys know if I have any other questions / feedback about the setup! Thanks so much again! 🙏

from jackson.

Sneak peek of the release: https://twitter.com/steventey/status/1688241881417973761

Massive shoutout to y'all for doing an amazing job at demystifying esoteric concepts like Enterprise SSO and Directory sync: https://twitter.com/steventey/status/1688241887076102144

from jackson.

@steven-tey Great to hear.:) We'll look at keeping everything in the same database and post back. Generally not an issue as long as the migrations don't conflict.

from jackson.

Thanks for reporting this @steven-tey, we'll look into this issue.

from jackson.

@steven-tey Could you provide more context around this? Are you hitting the same error while trying out a specific operation if so which one?

from jackson.

@niwsa I basically followed the instructions here to set up the missing tables (jackson_index, jackson_store and jackson_ttl) in the Prisma schema from the SaaS starter kit.

And I'm using the following as the JacksonOption (swapping out postgres for Planetscale MySQL):

const samlAudience = "https://saml.dub.sh";
const samlPath = "/api/auth/saml/acs";

const opts: JacksonOption = {
  externalUrl: process.env.NEXTAUTH_URL as string,
  samlPath,
  samlAudience,
  db: {
    engine: "sql",
    type: "mysql",
    url: process.env.DATABASE_URL as string,
    ssl: {
      rejectUnauthorized: false,
    },
  },
  idpEnabled: true,
  clientSecretVerifier: process.env.NEXTAUTH_SECRET as string,
};

I'm also curious if it's a best practice to use Jackson in the same database as your application's main database, or would it be better to use it in a separate database? If the latter, how do you make sure both databases are in sync?

from jackson.

@steven-tey Aah could you please try engine: "planetscale", - https://boxyhq.com/docs/jackson/deploy/service#planetscale

Regarding Jackson db it is ideal to keep it separate and run the migration scripts we provide. But you bring up a good point, we can add it to the Prisma schema of SaaS starter kit (cc: @niwsa @devkiran) so that is in sync. When we update the Jackson lib we can continue to keep the schema in sync.

from jackson.

@deepakprabhakara – ahh nice, that fixed it 😄

It looks like the SaaS starter kit has both the Jackson DB and the main DB (that uses the Prisma schema) in the same database – are there any downsides to that? I'm currently using Planetscale MySQL and would love to keep everything in one database if possible 😃

from jackson.