DEV Community: Monte Logic

Setting Up Turso with Next.js and Prisma

Monte Logic — Fri, 18 Oct 2024 20:04:01 +0000

There are two ways which you can use Turso, locally and through a connection

Locally:

datasource db {
provider = "sqlite"
url = "file:./dev.db"
}

Once you run, npx prisma generate, your dev.db file should be created and you’re ready for local development.

Through a connection (Turso’s db)

In order to do it through a connection we need to install the Turso CLI. Installing the CLI, should be a simple process, with the official instructions.
Understanding the limitations.

“Since libSQL uses HTTP to connect to the remote database, this makes it incompatible with Prisma Migrate. However, you can use prisma migrate diff to create a schema migration and then apply the changes to your database using Turso’s CLI.

“

This messes up the Developer Experience but with most of the work being focused on Drizzle lets be glad that we have workarounds to use Prisma.

We wrote down the migration script which can be found in the official video on using Prisma with Turso.

npx prisma migrate diff --from-empty --to-schema-datamodel prisma/schema.prisma --script > baseline.sql

The above command will create a .sql file called baseline.sql.

Then, we run this command:

turso db shell your-database < baseline.sql

Connecting with libraries

The two libraries we need can be downloaded with this command:

npm install @libsql/client @prisma/adapter-libsql

To push the db, run:

npx prisma db push

After all of this your Turso with Next.js and Prisma app should work fine.
Errors:

“Error: failed to execute SQL:
error code 401: Not authorized to execute query: DDL statements not permitted on namespace f16a969f-77b1-4020-9701-b595ea037277″

Fix: Be careful so that your are operating db schema, not the db which is a “child db”. Again, operate on the schema level db.
To Conclude,

I would not recommend using Turso with Prisma, it is much better to use Turso with Drizzle.

Best Next.js Devs who create content

Monte Logic — Wed, 27 Mar 2024 15:42:22 +0000

As you get climb the ladder of skills it becomes harder and harder to get higher and higher.

The people you can gain lots of knowledge becomes shorter and shorter, so here are the devs that I view have spent at least 10,000 hours on the Next.js stack or closely related stacks to call themselves an Expert or a Master in Next.js.

Remi Wg
https://dev.to/ixartz

Cosden Solutions
https://cosden.solutions/

Gemini is hot garbage for writing code.

Monte Logic — Sun, 25 Feb 2024 17:13:28 +0000

The fact that Google can put that LLM out and even hint at it being able to write code is making us as a tech industry lose credibility.

Look at these prompts and how Gemini isn't doing anything but stating the obvious.

"
profile picture
For this:
"
{
"midDay": [],
"afternoon": [],
"midMorning": [
"Today, we had more issues with the lift gate and we were 25 minutes late arriving to the post office and 20 minutes late, finishing the route. "
],
"earlyMorning": []
}

Me:
"
And two image urls to midMorning which will be accessed via midMorning["imgURL"'][0]
The variables will be set using setState in .tsx.
"
Gemini:
"
I'd be glad to help you with that! However, I need some clarification to provide the best possible assistance:

Clarification Needed:

Purpose of the Data: What is the overall goal of storing this information about delivery delays in different timeframes? Is it for tracking performance, reporting to clients, or something else? Understanding the purpose will help tailor the solution accordingly.

"
Me:
"
" const [summaryObject, setSummaryObject] = useState(null); // Initialize with null

                   <textarea
                       className="text-gray-900"
                       id="newSummaryInputID"
                       name="newSummaryInputName"
                       value={summaryObject && summaryObject.earlyMorning} // Check if routeSummary is not null before accessing routeSummary.routeSummary
                       onChange={(e) => {
                           // Ensure setRouteSummary is updating the state correctly
                           setSummaryObject((prevSummaryObject: ObjectSummary | null) => ({
                               ...prevSummaryObject,
                               earlyMorning: [e.target.value],
                               midMorning: prevSummaryObject?.midMorning ?? [], // Ensure midMorning is always an array
                               midDay: prevSummaryObject?.midDay ?? [], // Ensure midDay is always an array
                               afternoon: prevSummaryObject?.afternoon ?? [], // Ensure afternoon is always an array
                           }));
                       }}
                   />

Gemini:
"
The provided code snippet shows how to manage a state object named summaryObject using the useState hook in React. It also demonstrates the usage of a controlled textarea component. While I don't have the full context of your application, I can offer some analysis and suggestions based on the provided code:

All that crap and not a single line of code wrote, meanwhile OLD ChatGPT is offering way better suggestions.
I asked ChatGPT the same thing and it provided a useful interface among many other USEFUL things.
The interface:
"
interface ObjectSummary {
midDay: string[];
afternoon: string[];
midMorning: { text: string; imgURL?: string }[];
earlyMorning: string[];
}