[libsql] Add null check to normalizeRow

[lightyaer]

A simple null check for normalizeRow function in libsql.

Fixes: #1049

let me know if this is a correct fix, I'm happy to learn more about this and implement any suggestions.
Thanks.

[dankochetov]

Please add a test that verifies this behavior.

[lightyaer]

@dankochetov
I found out that the normalizedRow function gets undefined, when we don't use returning() before get(),

We do have type-tests for this, but this behaviour is kinda weird, ideally, we shouldn't have a get() function in intellisense (dropdown on a dot after a function in IDE) incase of libsql after the values(), onConflictDoNothing() and onConflictDoUpdate(), incase of libsql.

I have changed the PR to throw an error incase we use get() without returning() in libsql.

Let me know, if the error message is good to go.

Code used to reproduce the error:

      const x = {
            id: "asd",
            createdAt: new Date().toISOString(),
            email: "[email protected]",
            emailVerified: new Date().toISOString(),
            updatedAt: new Date().toISOString(),
            name: "asdasd",
            picture: "asdasd",
            username: "asdoihsdfo",
        };

        const newUser = await db
            .insert(users)
            .values(x)
            .onConflictDoUpdate({
                target: users.email,
                set: {
                    email: `${new Date().getTime()}@gmail.com`,
                    id: `${new Date().getTime()}-sodhfoh`,
                    updatedAt: new Date().toString(),
                    name: `askd${new Date().getTime()}`,
                },
            })
            // no returning()
            .get()
           


        console.log(newUser.id);

The following images show when id is being accessed from newUser

In webstorm

In vscode.

[lightyaer]

closing out his PR since the purpose of this was fulfilled elsewhere.