Postgresql is case case insensitive unless you impose a specific casing
using " (double quotes): they are valid everywhere postgresql expects an
identifier (schema name, table name, column name, cte name, after AS, etc.
So it's all correct.
See
I see.
I didn't expect it to be so simple.
I tried to debug sqlalchemy, but didn't find character conversion
It turned out to be the default way of postgreql.
Thanks for your instruction.
'Jonathan Vanasco' via sqlalchemy 於 2022/4/1 04:47 寫道:
I'm not aware of any recent changes in the libraries
I'm not aware of any recent changes in the libraries that would cause that
behavior.
It may be how you are using the libraries or raw sql.
PostgreSQL will convert database names to lowercase UNLESS the database
name is in quotes.
These will all create `abc`:
CREATE DATABASE abc;
Hi everyone, I have a question
I use Postgresql
Before creating a database, the name is uppercase and lowercase, and there
is no problem.
Later SQLAlchemy was updated to version 1.4
Don't know when the version started,
When creating a database again, use uppercase and lowercase names, which
Works! Thank you!
четверг, 31 марта 2022 г. в 15:42:25 UTC+3, Mike Bayer:
> when using multiprocessing, the connection pool in the new process must be
> replaced with a new one. This is usually accomplished by calling
> engine.dispose(). However, to maintain the pool in the parent
when using multiprocessing, the connection pool in the new process must be
replaced with a new one. This is usually accomplished by calling
engine.dispose(). However, to maintain the pool in the parent process as well,
replace the connection pool alone without disposing the old one:
Hello!
>From time to time, I need to update data in tables and multiprocessing can
speed up this process. Last example: I’m trying to update data 7M rows in
table
SQLAlchemy 1.4.31, psycopg2 2.8.6, PostgreSQL
def job_update_rd(data_list):
updated = []
with Session() as session:
