Registration Error Er_Bad_Field_Error Unknown Column preferredLanguage in field list

[staart]

Registration Error Er_Bad_Field_Error Unknown Column preferredLanguage in field list

[AnandChowdhary]

Thanks for opening this issue, @wayneburlingame! It makes me really happy that you got excited about the "end-to-end" SaaS, that was precisely my intention.

The database schema is for 1.x, so if you use that, everything should work. It seems like you're using 2.x, which uses a different schema, where the preferredLanguage column has been renamed to prefersLanguage to match other columns with the "prefers" prefix for color scheme and reduced motion.

If you want to use 2.x, you should use the Prisma schema to generate your database (docs for that coming soon!) and you should use the new branch in Staart UI rather than master. You can use npx prisma migrate up --experimental to generate your database instead of the schema.sql you must be using now.

Let know if this solves your problem! I'll keep this issue open until I have decent "getting started" docs for the new version with Prisma.

[AnandChowdhary]

In summary, your options are, though it's my fault this is so confusing:

1. master branch of API with new, upcoming version of Staart UI (in v2 branch)
2. 1.x version of API with Staart UI's master branch

What you're doing is master branch of API with the master branch of UI, which sadly doesn't work (though I'll make sure it does soon!). I think the best way forward is to update your Staart UI to the v2 branch. :)

[wayneburlingame]

Anand, I am excited and have been up all night trying to get this to work. Yes, there is too many inconsistencies with all the documentation, and somehow I grabbed a bit of the new info and somewhere a bit of the old, and I think I mingled them together. A newer full walk-through document would greatly help out. I almost figured it out and I do not understand npm, yarn, etc.... and how it all works very good. But, I have already blown my current clone/build and have the new one rebuild, but I am missing a few things ( Getting errors) 1 question for now... How do I build the Prisma Schema for the database, or make MySQL do it? I'm not at all familiar with it, but while waiting for a reply I will be looking it up. Thank You, Wayne <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

…

On Sun, May 10, 2020 at 11:40 AM Anand Chowdhary ***@***.***> wrote: In summary, your options are, though it's my fault this is so confusing: 1. master branch of API with new, upcoming version of Staart UI (in v2 branch) 2. 1.x version of API with Staart UI's master branch What you're doing is master branch of API with the master branch of UI, which sadly doesn't work (though I'll make sure it does soon!). I think the best way forward is to update your Staart UI to the v2 branch. :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#873 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE5W64S6EJRNKE7AC6BFVNDRQ3KH3ANCNFSM4M5HIIUQ> .

-- Thank You, Wayne Burlingame

[AnandChowdhary]

You can use npx prisma migrate up --experimental to generate your database instead of the schema.sql you must be using now.

Prisma Migrate docs: https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-migrate

[wayneburlingame]

Anand, At this moment, this is too complicated for me in regards to the database to Prisma setup. I am really green when it comes to them, and not much experience. I'm willing to help though but would need more info. Do you have documentation on all the reference points that need tables or info created in the database? I think I can find someone to do all the Database to Prisma schema, so everything in the UI template website would work. Either that, or I need to wait until someone else offers a template. :) AKA

>> YOU LOL or someone else.

You know, before adding any other features, and just using what you already have coded and get all database scheme created for everything vanilla/defacto setup. That way you have a quick template for people to drop in and use. Also, on your documentation, you refer to MySQL/MariaDB, but Prisma uses a lot of *PostgreSQL* in their documentation and tutorials and examples, and have a connector to Heroku because you can get a free Heroku account with *PostgreSQL* do I did not know if it is critical, to just switch and say PostgreSQL in the documentation setup or if it affects the other Staart components.

…

On Sun, May 10, 2020 at 2:58 PM Anand Chowdhary ***@***.***> wrote: You can use npx prisma migrate up --experimental to generate your database instead of the schema.sql you must be using now. Prisma Migrate docs: https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-migrate — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#873 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE5W64RH3FWGE2UUF5Y4U6LRQ4BQDANCNFSM4M5HIIUQ> .

-- Thank You, Wayne Burlingame

[AnandChowdhary]

Do you have documentation on all the reference points that need tables or
info created in the database?

Yes, the prisma/schema.prisma file in Staart API has the Prisma schema about what tables should be created and the general data structure and relations.

Also, on your documentation, you refer to MySQL/MariaDB, but Prisma uses a lot of PostgreSQL in their documentation and tutorials and examples

This project uses MySQL, but the point of Prisma is that it works with many different databases. Although they have some examples with Postgres, they also have examples with MySQL and others. In the schema.prisma file, you'll notice that we're using MySQL.

I'll write a thorough "Getting started" guide soon and hopefully that'll make this process easier. :)

[wayneburlingame]

You'll be glad for writing the guide. It will greatly reduce all the nagging questions.

…

On Mon, May 11, 2020, 4:54 AM Anand Chowdhary ***@***.***> wrote: Do you have documentation on all the reference points that need tables or info created in the database? Yes, the prisma/schema.prisma file in Staart API has the Prisma schema about what tables should be created and the general data structure and relations. Also, on your documentation, you refer to MySQL/MariaDB, but Prisma uses a lot of *PostgreSQL* in their documentation and tutorials and examples This project uses MySQL, but the point of Prisma is that it works with many different databases. Although they have some examples with Postgres, they also have examples with MySQL and others. In the schema.prisma file, you'll notice that we're using MySQL. I'll write a thorough "Getting started" guide soon and hopefully that'll make this process easier. :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#873 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE5W64SEL5AJH5VV4XXEAE3RQ7DO3ANCNFSM4M5HIIUQ> .

[FindingAnand]

⚠️ This issue has not seen any activity in the past 2 months so I'm marking it as stale. I'll close it if it doesn't see any activity in the coming week.