PostgreSQL: "incorrect binary data format in bind parameter x"

To reproduce, import this (pasted below) SQL into a Postgres database.

create extension if not exists "pgcrypto";

create or replace function set_updated_at() RETURNS trigger
  LANGUAGE plpgsql
  AS $$
begin
  new.updated_at := current_timestamp;
  return new;
end;
$$;

create table if not exists users (
  id uuid primary key not null default gen_random_uuid(),
  "name" text not null,
  handle text not null,
  created_at timestamp not null default now(),
  updated_at timestamp not null default now()
);
create trigger updated_at before update on users for each row execute procedure set_updated_at();

create table if not exists locations (
  id uuid primary key not null default gen_random_uuid(),
  latitude float not null,
  longitude float not null
);

create table if not exists tweets (
  id uuid primary key not null default gen_random_uuid(),
  created_at timestamp not null default now(),
  "text" text not null,
  "owner" uuid not null references users(id) on delete cascade,
  "location" uuid not null references locations(id) on delete cascade
);

Introspect this database

prisma2 introspect --url 'postgresql://root:prisma@localhost:5432/basic-twitter?schema=public'

Run the following client call:

const { PrismaClient } = require('@prisma/client')

const prisma = new PrismaClient()

async function main() {
  const data = await prisma.locations.create({
    data: {
      id: 'f70c6744-c2cb-5a28-b4c6-5aa0680dac0c',
      latitude: 234.96,
      longitude: -391.52,
    },
  })
  console.log(data)
}

main().finally(() => prisma.disconnect())

Error observed:

Invalid `prisma.locations.create()` invocation in 
./index.js:6:60 
 
Error occurred during query execution: 
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(Error { kind: Db, cause: Some(DbError { severity: "ERROR", parsed_severity: Some(Error), code: SqlState("22P03"), message: "incorrect binary data format in bind parameter 1", detail: None, hint: None, position: None, where_: None, schema: None, table: None, column: None, datatype: None, constraint: None, file: Some("postgres.c"), line: Some(1828), routine: Some("exec_bind_message") }) }) }) 
  at ​index.js:6:2​
  at ​​​processTicksAndRejections​​​ ​internal/process/task_queues.js:85​

---

Internal notes:

Test utils database(s) affected:

• https://github.com/prisma/introspection-engine-output/blob/test_utils/test-utils/results/postgresql_public_test_utils_basic-twitter_stderr.log
• https://github.com/prisma/introspection-engine-output/blob/test_utils/test-utils/results/postgresql_public_test_utils_jira_stderr.log
• https://github.com/prisma/introspection-engine-output/blob/test_utils/test-utils/results/postgresql_public_test_utils_sportsdb_stderr.log

[divyenduz]

This one is no longer reproducible on the latest alpha (starting with 902)

divyendusingh [introspection-engine-output]$ prisma2 --version
prisma2@2.0.0-alpha.902, binary version: 7f34f2252d46d463cf9a2e45488385c5adb0a49b

[divyenduz]

Yes! We should