Datasets:

akumoth

/

peewee-issues

like 0

https://api.github.com/repos/coleifer/peewee/issues/2719

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2719/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2719/comments

https://api.github.com/repos/coleifer/peewee/issues/2719/events

https://github.com/coleifer/peewee/issues/2719

I_kwDOAA7yGM5k5jUa

PeeWee ForeignKeyField error. IntegrityError: (1215, 'Cannot add foreign key constraint')

closed

NONE

I have code like below: ``` import datetime import peewee as pw import os my_db = pw.MySQLDatabase(database=os.getenv("DB_NAME"), host=os.getenv("DB_HOST"), port=os.getenv("DB_PORT"), user=os.getenv("DB_USER"), passwd=os.getenv("DB_PASSWORD") class MySQLModel(pw.Model): """A base model class that will use MySQL""" class Meta: database = my_db class UnsignedBigAutoField(pw.BigAutoField): field_type = 'BIGINT UNSIGNED UNIQUE AUTO_INCREMENT' class UnsignedAutoField(pw.AutoField): field_type = 'INT UNSIGNED UNIQUE AUTO_INCREMENT' class User(MySQLModel): id = UnsignedBigAutoField(primary_key=True) alias = pw.CharField(max_length=16, unique=True, null=False) date_created = pw.DateTimeField(default=datetime.datetime.now) class Ticket(MySQLModel): id = UnsignedBigAutoField(primary_key=True) user = pw.ForeignKeyField(User, backref="tickets", field="id", on_delete="RESTRICT", on_update="CASCADE") date_created = pw.DateTimeField(default=datetime.datetime.now) my_db.create_tables([User, Ticket]) ``` The last line of the code when creating ForeignKey produces error: > peewee.IntegrityError: (1215, 'Cannot add foreign key constraint') I checked the datatype(Bitint), and unique/non-null flag are all setup correctly for User table. Couldn't figure out what went wrong here. I created the ForeignKey in MySqlWorkBench manually in Ticket table without a problem. Any help would be appreciated.

https://api.github.com/repos/coleifer/peewee/issues/2719/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2718

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2718/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2718/comments

https://api.github.com/repos/coleifer/peewee/issues/2718/events

https://github.com/coleifer/peewee/issues/2718

I_kwDOAA7yGM5k5jEt

Fastapi db connection doc

closed

NONE

Hi, Here's the peewee doc I'm referring to: https://docs.peewee-orm.com/en/latest/peewee/database.html#fastapi According to the FastAPI doc, the startup & shutdown events are for when the application, not request here: https://fastapi.tiangolo.com/advanced/events/#startup-event Let me know I'm missing something, new here.

https://api.github.com/repos/coleifer/peewee/issues/2718/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2717

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2717/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2717/comments

https://api.github.com/repos/coleifer/peewee/issues/2717/events

https://github.com/coleifer/peewee/issues/2717

I_kwDOAA7yGM5kxnoK

Calling save fails when PK is provided but record does not exist yet.

closed

NONE

In this example: ```python class CustomerPeewee(BaseModel): email = CharField() class Meta: db_table = "customer" customer = CustomerPeewee() customer.id = 4 customer.email = "example@example.com" customer.save() ``` No record is created and 0 is returned. If this is intended it feels counter intuitive as the docs seem to make no mention of this behaviour not being possible

https://api.github.com/repos/coleifer/peewee/issues/2717/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2716

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2716/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2716/comments

https://api.github.com/repos/coleifer/peewee/issues/2716/events

https://github.com/coleifer/peewee/issues/2716

I_kwDOAA7yGM5kj6nC

Automatic Migrations Capability

closed

NONE

Hey there! Anuran this side! I'm a long time fan of peewee, been using it for a quite a few projects - thanks for this awesome tool, really saves a lot of time for someone who uses Django as well! 🚀 Actually I was on the process of creating a custom script for automated migrations, since I couldn't find any automated tool for migrations, so I decided to create one. I was going through the codebase of peewee - it's pretty neat. I wonder why an automated migrations haven't been added yet, especially given that `playhouse.migrate` does exist. Can I go forward and develop an `AutoMigrator` object, that depends on the objects provided by `playhouse.migrate`?

https://api.github.com/repos/coleifer/peewee/issues/2716/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2715

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2715/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2715/comments

https://api.github.com/repos/coleifer/peewee/issues/2715/events

https://github.com/coleifer/peewee/issues/2715

I_kwDOAA7yGM5kcw6q

Postgres error : Driver not installed, using peewee,docker and fastapi

closed

NONE

I have installed peewee 3.16.2 ,pyscopg2 66.0.2 and fastapi 0.95.1. I follow the steps in peewee docs about integrate fastapi apps, but showing up this error **peewee.ImproperlyConfigured: Postgres driver not installed!** This is my config file in fastapi: def init_db(): db = PostgresqlDatabase( 'atlas_repos', user='atlas', password='password', host='localhost', port=5432) return db this function is called from a main.py in fastapi where I have a db.connect() function Any help would be much apreciated.

https://api.github.com/repos/coleifer/peewee/issues/2715/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2714

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2714/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2714/comments

https://api.github.com/repos/coleifer/peewee/issues/2714/events

https://github.com/coleifer/peewee/issues/2714

I_kwDOAA7yGM5kPexl

`peewee` for WebAssembly (JupyterLite + XEUS-Python + emscripten-forge)

closed

NONE

## Overview To bring the [Brightway life-cycle assessment python package](https://documentation.brightway.dev/) to the browser, [we](https://github.com/brightway-lca) recently added `peewee` to the WebAssembly [`emscripten-forge`](https://github.com/emscripten-forge/recipes) package repository. This was necessary since `peewee` comes with C extensions (more specifically, it is using [`psycopg2cffi`](https://github.com/coleifer/peewee/blob/c825a0fb11b1dae1f88d93c67f2fbcb4a34d4ad4/peewee.py#L43)). `emscripten-forge` is an alternative to the monolythic [Pyodide](https://pyodide.org/en/stable/index.html) Python WebAssembly distribution that is best described [in this article by the core development team.](https://blog.jupyter.org/mamba-meets-jupyterlite-88ef49ac4dc8) ## Error Unfortunately, I get an error when running it in a [JupyterLite](https://jupyterlite.readthedocs.io/en/latest/) XEUX-Python hub. While this is likely out-of-scope for the developers of `peewee`, I would be very grateful for any hints on the potential root cause. It might be realated to [the filesystem of JupyterLite](https://jupyterlite.readthedocs.io/en/latest/search.html?q=filesystem). ``` from peewee import * # Define a database object db = SqliteDatabase('my_database.db') # Define a model class class Person(Model): name = CharField() age = IntegerField() class Meta: database = db # Create the table in the database db.connect() db.create_tables([Person]) person1 = Person(name='Alice', age=25) person1.save() ``` returnes: ``` DatabaseError: database disk image is malformed ``` <details> <summary>Full Error Message</summary> ``` --------------------------------------------------------------------------- DatabaseError Traceback (most recent call last) /tmp/xeus-python-kernel/envs/xeus-python-kernel/lib/python3.10/site-packages/peewee.py in execute_sql(self, sql, params, commit) 3235 cursor = self.cursor() -> 3236 cursor.execute(sql, params or ()) 3237 return cursor DatabaseError: database disk image is malformed During handling of the above exception, another exception occurred: DatabaseError Traceback (most recent call last) /tmp/xpython_42/2390659374.py in <cell line: 2>() 1 person1 = Person(name='Alice', age=25) ----> 2 person1.save() /tmp/xeus-python-kernel/envs/xeus-python-kernel/lib/python3.10/site-packages/peewee.py in save(self, force_insert, only) 6745 rows = self.update(**field_dict).where(self._pk_expr()).execute() 6746 elif pk_field is not None: -> 6747 pk = self.insert(**field_dict).execute() 6748 if pk is not None and (self._meta.auto_increment or 6749 pk_value is None): /tmp/xeus-python-kernel/envs/xeus-python-kernel/lib/python3.10/site-packages/peewee.py in inner(self, database, *args, **kwargs) 1960 raise InterfaceError('Query must be bound to a database in order ' 1961 'to call "%s".' % method.__name__) -> 1962 return method(self, database, *args, **kwargs) 1963 return inner 1964 /tmp/xeus-python-kernel/envs/xeus-python-kernel/lib/python3.10/site-packages/peewee.py in execute(self, database) 2031 @database_required 2032 def execute(self, database): -> 2033 return self._execute(database) 2034 2035 def _execute(self, database): /tmp/xeus-python-kernel/envs/xeus-python-kernel/lib/python3.10/site-packages/peewee.py in _execute(self, database) 2836 self._returning = (self.table._primary_key,) 2837 try: -> 2838 return super(Insert, self)._execute(database) 2839 except self.DefaultValuesException: 2840 pass /tmp/xeus-python-kernel/envs/xeus-python-kernel/lib/python3.10/site-packages/peewee.py in _execute(self, database) 2549 cursor = self.execute_returning(database) 2550 else: -> 2551 cursor = database.execute(self) 2552 return self.handle_result(database, cursor) 2553 /tmp/xeus-python-kernel/envs/xeus-python-kernel/lib/python3.10/site-packages/peewee.py in execute(self, query, commit, **context_options) 3242 ctx = self.get_sql_context(**context_options) 3243 sql, params = ctx.sql(query).query() -> 3244 return self.execute_sql(sql, params) 3245 3246 def get_context_options(self): /tmp/xeus-python-kernel/envs/xeus-python-kernel/lib/python3.10/site-packages/peewee.py in execute_sql(self, sql, params, commit) 3232 __deprecated__('"commit" has been deprecated and is a no-op.') 3233 logger.debug((sql, params)) -> 3234 with __exception_wrapper__: 3235 cursor = self.cursor() 3236 cursor.execute(sql, params or ()) /tmp/xeus-python-kernel/envs/xeus-python-kernel/lib/python3.10/site-packages/peewee.py in __exit__(self, exc_type, exc_value, traceback) 3008 new_type = self.exceptions[exc_type.__name__] 3009 exc_args = exc_value.args -> 3010 reraise(new_type, new_type(exc_value, *exc_args), traceback) 3011 3012 /tmp/xeus-python-kernel/envs/xeus-python-kernel/lib/python3.10/site-packages/peewee.py in reraise(tp, value, tb) 190 def reraise(tp, value, tb=None): 191 if value.__traceback__ is not tb: --> 192 raise value.with_traceback(tb) 193 raise value 194 /tmp/xeus-python-kernel/envs/xeus-python-kernel/lib/python3.10/site-packages/peewee.py in execute_sql(self, sql, params, commit) 3234 with __exception_wrapper__: 3235 cursor = self.cursor() -> 3236 cursor.execute(sql, params or ()) 3237 return cursor 3238 DatabaseError: database disk image is malformed ``` </details> ## Reproduce Error Access the JupyterLite Hub and open `peewee_test.ipynb` at https://michaelweinold.github.io/hub/ ## Related - https://github.com/emscripten-forge/recipes/issues/295 - https://github.com/emscripten-forge/recipes/pull/322

https://api.github.com/repos/coleifer/peewee/issues/2714/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2713

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2713/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2713/comments

https://api.github.com/repos/coleifer/peewee/issues/2713/events

https://github.com/coleifer/peewee/issues/2713

I_kwDOAA7yGM5kMK0B

How to "NOT" create index on a "unique" field

closed

NONE

i have o model looking like this. ``` class User(BaseModel): id = BigIntegerField(unique=True) first_name = TextField() last_name = CharField(null=True) username = CharField(unique=True, null=True, index=False) phone = CharField(null=True) deleted = BooleanField(null=True) is_bot = BooleanField(null=True) bio = CharField(null=True) photo = TextField(null=True) roles = BigIntegerField() ``` After tables are created when i check db file with sqlstudio i saw "username" index on user table. I dont want this, it is unique but should be null as well. I'm getting "UNIQUE constraint failed: user.username" error when I try to update or create a user without a username second time. I believe that index is the cause. <img width="870" alt="Screen Shot 2023-04-24 at 13 03 17" src="https://user-images.githubusercontent.com/38407276/233966648-e8504dc1-a15d-4fc8-974e-ad0f4ae42bba.png">

https://api.github.com/repos/coleifer/peewee/issues/2713/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2712

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2712/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2712/comments

https://api.github.com/repos/coleifer/peewee/issues/2712/events

https://github.com/coleifer/peewee/issues/2712

I_kwDOAA7yGM5kKrv9

insert_many method missing field values.

closed

NONE

peewee==3.16.0 Python 3.10.6 For the following code: ``` class TestModel(Model): class Meta: database = mysql_db test_field = CharField(null=True) TestModel.create_table() insert_data = [ {}, { 'test_field': "hello" } ] TestModel.insert_many(insert_data).execute() ``` Result: ``` id test_field 1 NULL 2 NULL ``` The test_field field of the second record was not inserted. The following is the modified code: ``` class TestModel(Model): class Meta: database = mysql_db test_field = CharField(null=True) TestModel.create_table() insert_data = [{ 'test_field': None },{ 'test_field': "hello" } ] TestModel.insert_many(insert_data).execute() ``` It worked ``` id test_field 1 NULL 2 hello ``` Is it by design? This goes against my instincts. Thank you for working on such an easy-to-use ORM framework

https://api.github.com/repos/coleifer/peewee/issues/2712/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2711

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2711/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2711/comments

https://api.github.com/repos/coleifer/peewee/issues/2711/events

https://github.com/coleifer/peewee/pull/2711

PR_kwDOAA7yGM5OwRRM

Feature/filter none on where

closed

NONE

```python q = SeriesTable.select().where( None, None ) ``` If where is called for the first time and where has more than one None parameter, an error will occur: ```shell Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/Users/ponponon/Desktop/code/me/gs_review_api/dev/peewee_in.py", line 32, in <module> q = SeriesTable.select().where( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/ponponon/.local/share/virtualenvs/gs_review_api-0lO5qGKr/lib/python3.11/site-packages/peewee.py", line 755, in inner method(clone, *args, **kwargs) File "/Users/ponponon/.local/share/virtualenvs/gs_review_api-0lO5qGKr/lib/python3.11/site-packages/peewee.py", line 2156, in where self._where = reduce(operator.and_, expressions) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TypeError: unsupported operand type(s) for &: 'NoneType' and 'NoneType' ``` So we filter the parameters of where and ignore those with the value None to avoid errors

https://api.github.com/repos/coleifer/peewee/issues/2711/timeline

https://api.github.com/repos/coleifer/peewee/issues/2710

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2710/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2710/comments

https://api.github.com/repos/coleifer/peewee/issues/2710/events

https://github.com/coleifer/peewee/pull/2710

PR_kwDOAA7yGM5OwDKO

feature: When `.in_(None)` is executed, the null condition should be …

closed

NONE

When `.in_(None)` is executed, the null condition should be ignored as `0 = 1`

https://api.github.com/repos/coleifer/peewee/issues/2710/timeline

https://api.github.com/repos/coleifer/peewee/issues/2709

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2709/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2709/comments

https://api.github.com/repos/coleifer/peewee/issues/2709/events

https://github.com/coleifer/peewee/issues/2709

I_kwDOAA7yGM5j0eOJ

db.atomic decorator is not a thread-safe

closed

NONE

Hello! peewee: 3.15.4 python: 3.10.8 Using db.atomic as decorator is not a thread-safe. The following example is showing that behaviour. ```python import logging import random import uuid from concurrent.futures import ThreadPoolExecutor from time import sleep import peewee from playhouse.pool import PooledPostgresqlExtDatabase db = PooledPostgresqlExtDatabase( database='test', user='postgres', password='postgres', host='localhost', ) logging.basicConfig( level=logging.DEBUG, format='[%(asctime)s] %(levelname)s [%(thread)s] %(message)s', datefmt='%Y-%m-%d %H:%M:%S', ) class User(peewee.Model): class Meta: database = db table_name = 'users' name = peewee.TextField() @db.atomic() def get_first(): sleep(random.randint(1, 3)) return User.select().first() def main(n): print(f'task {n}: start') with db.atomic(): User.insert(name=uuid.uuid4().hex).execute() get_first() with ThreadPoolExecutor(max_workers=5) as worker: worker.map(main, range(5)) ``` app logs ``` [2023-04-19 13:59:56] DEBUG [6174699520] No connection available in pool. [2023-04-19 13:59:56] DEBUG [6174699520] Created new connection 4365525936. [2023-04-19 13:59:56] DEBUG [6174699520] ('INSERT INTO "users" ("name") VALUES (%s) RETURNING "users"."id"', ['erika16']) [2023-04-19 13:59:56] DEBUG [6191525888] No connection available in pool. [2023-04-19 13:59:56] DEBUG [6191525888] Created new connection 4365526608. [2023-04-19 13:59:56] DEBUG [6191525888] ('INSERT INTO "users" ("name") VALUES (%s) RETURNING "users"."id"', ['qfritz']) [2023-04-19 13:59:56] DEBUG [6208352256] No connection available in pool. [2023-04-19 13:59:56] DEBUG [6174699520] ('SAVEPOINT "s36f6b1b9c9964d338b76086917abfa2c";', None) [2023-04-19 13:59:56] DEBUG [6191525888] ('SAVEPOINT "sf48e71a842874f81989e4b29ebb93c5b";', None) [2023-04-19 13:59:56] DEBUG [6208352256] Created new connection 4365526944. [2023-04-19 13:59:56] DEBUG [6208352256] ('INSERT INTO "users" ("name") VALUES (%s) RETURNING "users"."id"', ['paulanderson']) [2023-04-19 13:59:56] DEBUG [6225178624] No connection available in pool. [2023-04-19 13:59:56] DEBUG [6225178624] Created new connection 4365527280. [2023-04-19 13:59:56] DEBUG [6225178624] ('INSERT INTO "users" ("name") VALUES (%s) RETURNING "users"."id"', ['patricia09']) [2023-04-19 13:59:56] DEBUG [6242004992] No connection available in pool. [2023-04-19 13:59:56] DEBUG [6225178624] ('SAVEPOINT "s4ce9c8529df342a9ac71c47196be2567";', None) [2023-04-19 13:59:56] DEBUG [6242004992] Created new connection 4365527616. [2023-04-19 13:59:56] DEBUG [6242004992] ('INSERT INTO "users" ("name") VALUES (%s) RETURNING "users"."id"', ['christina08']) [2023-04-19 13:59:57] DEBUG [6208352256] ('SAVEPOINT "s33981849fd6345f69f7365c8279e4472";', None) [2023-04-19 13:59:57] DEBUG [6242004992] ('SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546";', None) [2023-04-19 13:59:57] DEBUG [6174699520] ('SELECT "t1"."id", "t1"."name" FROM "users" AS "t1" LIMIT %s', [1]) [2023-04-19 13:59:57] DEBUG [6174699520] ('RELEASE SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546";', None) [2023-04-19 13:59:57] DEBUG [6174699520] ('ROLLBACK TO SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546";', None) [2023-04-19 13:59:57] DEBUG [6191525888] ('SELECT "t1"."id", "t1"."name" FROM "users" AS "t1" LIMIT %s', [1]) [2023-04-19 13:59:57] DEBUG [6191525888] ('RELEASE SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546";', None) [2023-04-19 13:59:57] DEBUG [6191525888] ('ROLLBACK TO SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546";', None) [2023-04-19 13:59:58] DEBUG [6208352256] ('SELECT "t1"."id", "t1"."name" FROM "users" AS "t1" LIMIT %s', [1]) [2023-04-19 13:59:58] DEBUG [6208352256] ('RELEASE SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546";', None) [2023-04-19 13:59:58] DEBUG [6208352256] ('ROLLBACK TO SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546";', None) [2023-04-19 13:59:58] DEBUG [6242004992] ('SELECT "t1"."id", "t1"."name" FROM "users" AS "t1" LIMIT %s', [1]) [2023-04-19 13:59:58] DEBUG [6242004992] ('RELEASE SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546";', None) [2023-04-19 13:59:59] DEBUG [6225178624] ('SELECT "t1"."id", "t1"."name" FROM "users" AS "t1" LIMIT %s', [1]) [2023-04-19 13:59:59] DEBUG [6225178624] ('RELEASE SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546";', None) [2023-04-19 13:59:59] DEBUG [6225178624] ('ROLLBACK TO SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546";', None) ``` In the logs above, we're see, that threads are trying to release savepoint with an id it did not create. postgres logs: ``` 2023-04-19 10:59:56.522 UTC [61057] LOG: statement: BEGIN 2023-04-19 10:59:56.543 UTC [61057] LOG: duration: 23.928 ms 2023-04-19 10:59:56.549 UTC [61057] LOG: statement: INSERT INTO "users" ("name") VALUES ('erika16') RETURNING "users"."id" 2023-04-19 10:59:56.615 UTC [61057] LOG: duration: 68.462 ms 2023-04-19 10:59:56.626 UTC [61059] LOG: statement: BEGIN 2023-04-19 10:59:56.630 UTC [61059] LOG: duration: 6.580 ms 2023-04-19 10:59:56.636 UTC [61059] LOG: statement: INSERT INTO "users" ("name") VALUES ('qfritz') RETURNING "users"."id" 2023-04-19 10:59:56.637 UTC [61057] LOG: statement: SAVEPOINT "s36f6b1b9c9964d338b76086917abfa2c"; 2023-04-19 10:59:56.637 UTC [61057] LOG: duration: 0.593 ms 2023-04-19 10:59:56.678 UTC [61059] LOG: duration: 42.479 ms 2023-04-19 10:59:56.689 UTC [61059] LOG: statement: SAVEPOINT "sf48e71a842874f81989e4b29ebb93c5b"; 2023-04-19 10:59:56.691 UTC [61059] LOG: duration: 1.423 ms 2023-04-19 10:59:56.728 UTC [61061] LOG: statement: BEGIN 2023-04-19 10:59:56.732 UTC [61061] LOG: duration: 8.113 ms 2023-04-19 10:59:56.735 UTC [61061] LOG: statement: INSERT INTO "users" ("name") VALUES ('paulanderson') RETURNING "users"."id" 2023-04-19 10:59:56.819 UTC [61063] LOG: statement: BEGIN 2023-04-19 10:59:56.824 UTC [61063] LOG: duration: 6.820 ms 2023-04-19 10:59:56.828 UTC [61063] LOG: statement: INSERT INTO "users" ("name") VALUES ('patricia09') RETURNING "users"."id" 2023-04-19 10:59:56.922 UTC [61063] LOG: duration: 94.511 ms 2023-04-19 10:59:56.928 UTC [61063] LOG: statement: SAVEPOINT "s4ce9c8529df342a9ac71c47196be2567"; 2023-04-19 10:59:56.929 UTC [61063] LOG: duration: 0.893 ms 2023-04-19 10:59:56.981 UTC [61065] LOG: statement: BEGIN 2023-04-19 10:59:56.984 UTC [61065] LOG: duration: 5.307 ms 2023-04-19 10:59:56.987 UTC [61065] LOG: statement: INSERT INTO "users" ("name") VALUES ('christina08') RETURNING "users"."id" 2023-04-19 10:59:57.009 UTC [61061] LOG: duration: 274.434 ms 2023-04-19 10:59:57.015 UTC [61061] LOG: statement: SAVEPOINT "s33981849fd6345f69f7365c8279e4472"; 2023-04-19 10:59:57.015 UTC [61061] LOG: duration: 0.838 ms 2023-04-19 10:59:57.219 UTC [61065] LOG: duration: 232.845 ms 2023-04-19 10:59:57.222 UTC [61065] LOG: statement: SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:57.222 UTC [61065] LOG: duration: 0.481 ms 2023-04-19 10:59:57.644 UTC [61057] LOG: statement: SELECT "t1"."id", "t1"."name" FROM "users" AS "t1" LIMIT 1 2023-04-19 10:59:57.657 UTC [61057] LOG: duration: 13.231 ms 2023-04-19 10:59:57.661 UTC [61057] LOG: statement: RELEASE SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:57.662 UTC [61057] ERROR: savepoint "s97756b77a9264a9cbf194afde4f9e546" does not exist 2023-04-19 10:59:57.662 UTC [61057] STATEMENT: RELEASE SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:57.672 UTC [61057] LOG: statement: ROLLBACK TO SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:57.673 UTC [61057] ERROR: savepoint "s97756b77a9264a9cbf194afde4f9e546" does not exist 2023-04-19 10:59:57.673 UTC [61057] STATEMENT: ROLLBACK TO SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:57.677 UTC [61057] LOG: statement: ROLLBACK 2023-04-19 10:59:57.684 UTC [61057] LOG: duration: 6.259 ms 2023-04-19 10:59:57.695 UTC [61059] LOG: statement: SELECT "t1"."id", "t1"."name" FROM "users" AS "t1" LIMIT 1 2023-04-19 10:59:57.721 UTC [61059] LOG: duration: 26.199 ms 2023-04-19 10:59:57.724 UTC [61059] LOG: statement: RELEASE SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:57.726 UTC [61059] ERROR: savepoint "s97756b77a9264a9cbf194afde4f9e546" does not exist 2023-04-19 10:59:57.726 UTC [61059] STATEMENT: RELEASE SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:57.733 UTC [61059] LOG: statement: ROLLBACK TO SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:57.734 UTC [61059] ERROR: savepoint "s97756b77a9264a9cbf194afde4f9e546" does not exist 2023-04-19 10:59:57.734 UTC [61059] STATEMENT: ROLLBACK TO SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:57.741 UTC [61059] LOG: statement: ROLLBACK 2023-04-19 10:59:57.778 UTC [61059] LOG: duration: 37.320 ms 2023-04-19 10:59:58.023 UTC [61061] LOG: statement: SELECT "t1"."id", "t1"."name" FROM "users" AS "t1" LIMIT 1 2023-04-19 10:59:58.041 UTC [61061] LOG: duration: 18.985 ms 2023-04-19 10:59:58.045 UTC [61061] LOG: statement: RELEASE SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:58.046 UTC [61061] ERROR: savepoint "s97756b77a9264a9cbf194afde4f9e546" does not exist 2023-04-19 10:59:58.046 UTC [61061] STATEMENT: RELEASE SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:58.050 UTC [61061] LOG: statement: ROLLBACK TO SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:58.051 UTC [61061] ERROR: savepoint "s97756b77a9264a9cbf194afde4f9e546" does not exist 2023-04-19 10:59:58.051 UTC [61061] STATEMENT: ROLLBACK TO SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:58.054 UTC [61061] LOG: statement: ROLLBACK 2023-04-19 10:59:58.071 UTC [61061] LOG: duration: 17.898 ms 2023-04-19 10:59:58.228 UTC [61065] LOG: statement: SELECT "t1"."id", "t1"."name" FROM "users" AS "t1" LIMIT 1 2023-04-19 10:59:58.247 UTC [61065] LOG: duration: 20.065 ms 2023-04-19 10:59:58.249 UTC [61065] LOG: statement: RELEASE SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:58.250 UTC [61065] LOG: duration: 1.504 ms 2023-04-19 10:59:58.251 UTC [61065] LOG: statement: COMMIT 2023-04-19 10:59:58.254 UTC [61065] LOG: duration: 2.655 ms 2023-04-19 10:59:59.937 UTC [61063] LOG: statement: SELECT "t1"."id", "t1"."name" FROM "users" AS "t1" LIMIT 1 2023-04-19 10:59:59.957 UTC [61063] LOG: duration: 20.771 ms 2023-04-19 10:59:59.960 UTC [61063] LOG: statement: RELEASE SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:59.961 UTC [61063] ERROR: savepoint "s97756b77a9264a9cbf194afde4f9e546" does not exist 2023-04-19 10:59:59.961 UTC [61063] STATEMENT: RELEASE SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:59.964 UTC [61063] LOG: statement: ROLLBACK TO SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:59.964 UTC [61063] ERROR: savepoint "s97756b77a9264a9cbf194afde4f9e546" does not exist 2023-04-19 10:59:59.964 UTC [61063] STATEMENT: ROLLBACK TO SAVEPOINT "s97756b77a9264a9cbf194afde4f9e546"; 2023-04-19 10:59:59.966 UTC [61063] LOG: statement: ROLLBACK 2023-04-19 10:59:59.968 UTC [61063] LOG: duration: 1.987 ms ```

https://api.github.com/repos/coleifer/peewee/issues/2709/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2708

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2708/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2708/comments

https://api.github.com/repos/coleifer/peewee/issues/2708/events

https://github.com/coleifer/peewee/pull/2708

PR_kwDOAA7yGM5OSM0H

update pwiz add fields attr

closed

NONE

Issues #2707 : https://github.com/coleifer/peewee/issues

https://api.github.com/repos/coleifer/peewee/issues/2708/timeline

https://api.github.com/repos/coleifer/peewee/issues/2707

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2707/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2707/comments

https://api.github.com/repos/coleifer/peewee/issues/2707/events

https://github.com/coleifer/peewee/issues/2707

I_kwDOAA7yGM5jYhgm

pwiz generates detailed field attributes

closed

NONE

The peewee model generated by pwiz based on the database table is too simple， like： class NameModel(Model): name = CharField(null=True) status = IntegerField(default=11, index=True) class Meta: table_name = 'name_model' But generally we need more detailed field attributes，like (max_length, verbose): class NameModel(Model): name = CharField(max_length=128, null=True, verbose_name='name') status = IntegerField(default=11, index=True, verbose_name='status') class Meta: table_name = 'name_model'

https://api.github.com/repos/coleifer/peewee/issues/2707/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2706

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2706/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2706/comments

https://api.github.com/repos/coleifer/peewee/issues/2706/events

https://github.com/coleifer/peewee/issues/2706

I_kwDOAA7yGM5jWJS8

How to avoid fetch-then-create pattern, when fk id already known?

closed

NONE

New to Peewee... I'm sure this is easy but could not find an example in the docs In a case like this: ```python def start_game(user_id, subject: str) -> GameSession: user = User.get(User.id == user_id) game = GameSession.create(user=user, subject=subject) return game ``` How do I avoid first fetching the `User`, and instead create `GameSession` directly using the `user_id` already known for the foreign key field Is there something like Django's `user__id` relation-spanning syntax, or implicit `_id` suffixed fields for foreign keys?

https://api.github.com/repos/coleifer/peewee/issues/2706/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2705

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2705/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2705/comments

https://api.github.com/repos/coleifer/peewee/issues/2705/events

https://github.com/coleifer/peewee/issues/2705

I_kwDOAA7yGM5jK8Ud

Bitwise shift operators as functions?

closed

NONE

Hi, I know the Python operators `<<` and `>>` are overloaded in `peewee`. I'm wondering if there is some function (in `peewee.fn`) to use the [bitwise shift left/right operators in Postgresql](https://www.postgresql.org/docs/current/functions-bitstring.html). I've searched a lot but can't find anything myself. My use case is that I am doing a bitwise OR operation on a byte from a bytearray like this: ```python class Source(BaseModel): carton_flags = BigBitField() # search by a carton flag `cf` ... where=( fn.get_byte(self.carton_flags, fn.div(cf, 8).cast("integer")) ^ (1 << fn.mod(cf, 8).cast("integer")) ) ``` And I'm running into Python errors (`TypeError: unsupported operand type(s) for <<: 'int' and 'Cast'`), which forced me to use some ugly-ass `SQL()` unless I could find the bitwise left/right functions. Right now my workaround solution is to use ```python where=(fn.get_bit(self.carton_flags, cf) != 0) ``` but I'm wondering if there the bitwise left/right shift functions have been interfaced somewhere. Thanks

https://api.github.com/repos/coleifer/peewee/issues/2705/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2704

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2704/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2704/comments

https://api.github.com/repos/coleifer/peewee/issues/2704/events

https://github.com/coleifer/peewee/issues/2704

I_kwDOAA7yGM5jDASU

get_or_none() fails with postgres

closed

NONE

```py # Get shipping info from order.shipping_info_id shipping_info = {} if order.shipping_info: shipping_info = model_to_dict(ShippingInfo.get_or_none(order.shipping_info)) # no need to send id to client del shipping_info["id"] ``` Get_or_none with postgres raises `psycopg2.errors.DatatypeMismatch: argument of WHERE must be type boolean, not type integer` as the query built uses `WHERE 1` here is the full sql query : ``` SELECT "t1"."id", "t1"."country", "t1"."address", "t1"."postal_code", "t1"."city", "t1"."province" FROM "shippinginfo" AS "t1" WHERE 1 LIMIT 1 OFFSET 0' ``` I'm now using select and get as a temporary fix ```py # Get shipping info from order.shipping_info_id shipping_info = {} if order.shipping_info: shipping_info = model_to_dict(ShippingInfo.select().where(ShippingInfo.id == order.shipping_info.id).get()) # no need to send id to client del shipping_info["id" ``` Full stack trace : --- ``` functional_test.py:133 (TestPutShippingInfoOrder.test_put_order_valid_shipping_info) self = <peewee.PostgresqlDatabase object at 0x7f3d953e5a10> sql = 'SELECT "t1"."id", "t1"."country", "t1"."address", "t1"."postal_code", "t1"."city", "t1"."province" FROM "shippinginfo" AS "t1" WHERE %s LIMIT %s OFFSET %s' params = [1, 1, 0], commit = None def execute_sql(self, sql, params=None, commit=None): if commit is not None: __deprecated__('"commit" has been deprecated and is a no-op.') logger.debug((sql, params)) with __exception_wrapper__: cursor = self.cursor() > cursor.execute(sql, params or ()) E psycopg2.errors.DatatypeMismatch: argument of WHERE must be type boolean, not type integer E LINE 1: ..."t1"."province" FROM "shippinginfo" AS "t1" WHERE 1 LIMIT 1 ... E ^ ../../venv/lib/python3.11/site-packages/peewee.py:3236: DatatypeMismatch During handling of the above exception, another exception occurred: self = <Tests.functional_test.TestPutShippingInfoOrder object at 0x7f3d942c7310> client = <FlaskClient <Flask 'api.inf349'>> def test_put_order_valid_shipping_info(self, client): create_order(client) > response = client.put('/order/1', json={ "order": { "email": "elon.musk@spacex.com", "shipping_information": { "country": "Senegal", "address": "Rue des potiers", "postal_code": "G7H 0S5", "city": "Chicoutimi", "province": "QC" } } }) functional_test.py:136: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ../../venv/lib/python3.11/site-packages/werkzeug/test.py:1151: in put return self.open(*args, **kw) ../../venv/lib/python3.11/site-packages/flask/testing.py:223: in open response = super().open( ../../venv/lib/python3.11/site-packages/werkzeug/test.py:1095: in open response = self.run_wsgi_app(request.environ, buffered=buffered) ../../venv/lib/python3.11/site-packages/werkzeug/test.py:962: in run_wsgi_app rv = run_wsgi_app(self.application, environ, buffered=buffered) ../../venv/lib/python3.11/site-packages/werkzeug/test.py:1243: in run_wsgi_app app_rv = app(environ, start_response) ../../venv/lib/python3.11/site-packages/flask/app.py:2551: in __call__ return self.wsgi_app(environ, start_response) ../../venv/lib/python3.11/site-packages/flask/app.py:2531: in wsgi_app response = self.handle_exception(e) ../../venv/lib/python3.11/site-packages/flask/app.py:2528: in wsgi_app response = self.full_dispatch_request() ../../venv/lib/python3.11/site-packages/flask/app.py:1825: in full_dispatch_request rv = self.handle_user_exception(e) ../../venv/lib/python3.11/site-packages/flask/app.py:1823: in full_dispatch_request rv = self.dispatch_request() ../../venv/lib/python3.11/site-packages/flask/app.py:1799: in dispatch_request return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args) ../inf349.py:293: in order_id_handler return put_order() ../inf349.py:282: in put_order return update_shipping_order(payload["order"]) ../inf349.py:217: in update_shipping_order return get_order() ../inf349.py:162: in get_order shipping_info = model_to_dict(ShippingInfo.get_or_none(order.shipping_info)) ../../venv/lib/python3.11/site-packages/peewee.py:6634: in get_or_none return cls.get(*query, **filters) ../../venv/lib/python3.11/site-packages/peewee.py:6629: in get return sq.get() ../../venv/lib/python3.11/site-packages/peewee.py:7077: in get return clone.execute(database)[0] ../../venv/lib/python3.11/site-packages/peewee.py:1962: in inner return method(self, database, *args, **kwargs) ../../venv/lib/python3.11/site-packages/peewee.py:2033: in execute return self._execute(database) ../../venv/lib/python3.11/site-packages/peewee.py:2206: in _execute cursor = database.execute(self) ../../venv/lib/python3.11/site-packages/peewee.py:3244: in execute return self.execute_sql(sql, params) ../../venv/lib/python3.11/site-packages/peewee.py:3234: in execute_sql with __exception_wrapper__: ../../venv/lib/python3.11/site-packages/peewee.py:3010: in __exit__ reraise(new_type, new_type(exc_value, *exc_args), traceback) ../../venv/lib/python3.11/site-packages/peewee.py:192: in reraise raise value.with_traceback(tb) ```

https://api.github.com/repos/coleifer/peewee/issues/2704/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2703

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2703/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2703/comments

https://api.github.com/repos/coleifer/peewee/issues/2703/events

https://github.com/coleifer/peewee/issues/2703

I_kwDOAA7yGM5jC-JW

Failed constraints raises IntegrityError but exceeding max_length raises DataEror with postgres

closed

NONE

```py # shipping info model class ShippingInfo(BaseModel): id = peewee.AutoField(primary_key=True, unique=True) country = peewee.CharField(null=False) address = peewee.CharField(null=False) postal_code = peewee.CharField(null=False, max_length=7, constraints=[peewee.Check('length(postal_code) = 7')]) city = peewee.CharField(null=False) province = peewee.CharField(null=False) ``` I don't know if it's intended but it makes catching for errors a bit trickier ```py try: shipping_info_instance = ShippingInfo.create(**shipping_info) order.shipping_info = shipping_info_instance except peewee.IntegrityError, peewee.DataError: return errors.error_handler("orders", "invalid-fields", "Les informations d'achat ne sont pas correctes"), 422 ```

https://api.github.com/repos/coleifer/peewee/issues/2703/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2702

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2702/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2702/comments

https://api.github.com/repos/coleifer/peewee/issues/2702/events

https://github.com/coleifer/peewee/issues/2702

I_kwDOAA7yGM5jC8Ut

LIKE statement with postgres returns IndexError

closed

NONE

The like statement inside the email field is causing peewee to return an index error when constructing the database ```py class Order(BaseModel): id = peewee.AutoField(primary_key=True, unique=True) shipping_info = peewee.ForeignKeyField(ShippingInfo, backref='shipping_info', null=True) product = peewee.ForeignKeyField(Product, backref='product') email = peewee.CharField(null=True, constraints=[peewee.Check("email LIKE '%@%'")]) paid = peewee.BooleanField(null=False, default=False) credit_card = peewee.ForeignKeyField(CreditCard, backref='credit_card', null=True) transaction = peewee.ForeignKeyField(Transaction, backref='transaction', null=True) ``` ``` @pytest.fixture def client(): app.config['TESTING'] = True client = app.test_client() # init db db.connect() > db.create_tables([Product, ShippingInfo, Transaction, CreditCard, Order, OrderProduct]) conftest.py:16: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ../../venv/lib/python3.11/site-packages/peewee.py:3425: in create_tables model.create_table(**options) ../../venv/lib/python3.11/site-packages/peewee.py:6865: in create_table cls._schema.create_all(safe, **options) ../../venv/lib/python3.11/site-packages/peewee.py:5967: in create_all self.create_table(safe, **table_options) ../../venv/lib/python3.11/site-packages/peewee.py:5818: in create_table self.database.execute(self._create_table(safe=safe, **options)) ../../venv/lib/python3.11/site-packages/peewee.py:3244: in execute return self.execute_sql(sql, params) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <peewee.PostgresqlDatabase object at 0x7fe651b025d0> sql = 'CREATE TABLE IF NOT EXISTS "order" ("id" SERIAL NOT NULL PRIMARY KEY, "shipping_info_id" INTEGER, "product_id" INTEGE...KEY ("credit_card_id") REFERENCES "creditcard" ("id"), FOREIGN KEY ("transaction_id") REFERENCES "transaction" ("id"))' params = [], commit = None def execute_sql(self, sql, params=None, commit=None): if commit is not None: __deprecated__('"commit" has been deprecated and is a no-op.') logger.debug((sql, params)) with __exception_wrapper__: cursor = self.cursor() > cursor.execute(sql, params or ()) E IndexError: tuple index out of range ../../venv/lib/python3.11/site-packages/peewee.py:3236: IndexError ``` it seems that some other fields causes the indexError error but i can't precisely identify them also i noticed the error because i'm migrating from sqlite to postgres

https://api.github.com/repos/coleifer/peewee/issues/2702/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2701

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2701/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2701/comments

https://api.github.com/repos/coleifer/peewee/issues/2701/events

https://github.com/coleifer/peewee/issues/2701

I_kwDOAA7yGM5ix6j6

setup.py being deprecated

closed

NONE

This message is being displayed when pip installing peewee on python version 3.11.2: ``` DEPRECATION: peewee is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559 ```

https://api.github.com/repos/coleifer/peewee/issues/2701/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2700

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2700/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2700/comments

https://api.github.com/repos/coleifer/peewee/issues/2700/events

https://github.com/coleifer/peewee/issues/2700

I_kwDOAA7yGM5ivFjx

Create aware datetime objects for TimestampField

closed

NONE

**Description** With `TimestampField(utc=True)` it returns a naive datetime object. This is not recommended as they are treated by many datetime methods as local times. **Expected behaviour** Return an aware datetime object to avoid confusion, per the recommendation in [datetime docs](https://docs.python.org/3.11/library/datetime.html#datetime.datetime.utcfromtimestamp) **Suggested change** ```python if self.utc: - value = datetime.datetime.utcfromtimestamp(value) + value = datetime.datetime.fromtimestamp(value, datetime.timezone.utc) ```

https://api.github.com/repos/coleifer/peewee/issues/2700/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2699

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2699/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2699/comments

https://api.github.com/repos/coleifer/peewee/issues/2699/events

https://github.com/coleifer/peewee/issues/2699

I_kwDOAA7yGM5ieNCj

test_multiple_writers failing with database is locked on ppc64le arch

closed

NONE

Hello, The `tests.db_tests.TestThreadSafety.test_multiple_writers` test is failing on ppc64le architecture with: ``` peewee.OperationalError: database is locked ``` ``` + createdb peewee_test + psql -c 'CREATE EXTENSION hstore' peewee_test CREATE EXTENSION + /usr/bin/python3 runtests.py ...................................................................................s................ssssssssssssssssssssssssssssssssss...................s..........................sss............................................s.......ss............................s.................s........ssss..................................................................................s..........................................................................ssssss...........................ss..............................................s...................................................................................................................................................s.ss.................ssss............................................ss...............................s..................s...........ss...............................s....ss......s..............s..............................................................ss...............................................................Exception in thread Thread-47 (create_users): Traceback (most recent call last): File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 3236, in execute_sql Exception in thread Thread-46 (create_users): Traceback (most recent call last): File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 3236, in execute_sql cursor.execute(sql, params or ()) cursor.execute(sql, params or ()) sqlite3.OperationalError: database is locked During handling of the above exception, another exception occurred: sqlite3.OperationalError: database is locked During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib64/python3.11/threading.py", line 1038, in _bootstrap_inner Traceback (most recent call last): File "/usr/lib64/python3.11/threading.py", line 1038, in _bootstrap_inner self.run() File "/usr/lib64/python3.11/threading.py", line 975, in run self._target(*self._args, **self._kwargs) File "/builddir/build/BUILD/peewee-3.16.0/tests/db_tests.py", line 358, in create_users self.run() File "/usr/lib64/python3.11/threading.py", line 975, in run User.create(username='u%d' % i) File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 6537, in create self._target(*self._args, **self._kwargs) File "/builddir/build/BUILD/peewee-3.16.0/tests/db_tests.py", line 358, in create_users User.create(username='u%d' % i) File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 6537, in create inst.save(force_insert=True) File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 6747, in save inst.save(force_insert=True) File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 6747, in save pk = self.insert(**field_dict).execute() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 1962, in inner return method(self, database, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 2033, in execute return self._execute(database) ^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 2838, in _execute return super(Insert, self)._execute(database) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 2551, in _execute pk = self.insert(**field_dict).execute() cursor = database.execute(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 1962, in inner ^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 3244, in execute return method(self, database, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 2033, in execute return self._execute(database) return self.execute_sql(sql, params) ^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 3234, in execute_sql File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 2838, in _execute with __exception_wrapper__: File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 3010, in __exit__ reraise(new_type, new_type(exc_value, *exc_args), traceback) File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 192, in reraise return super(Insert, self)._execute(database) raise value.with_traceback(tb) File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 3236, in execute_sql ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 2551, in _execute cursor.execute(sql, params or ()) peewee.OperationalError: database is locked cursor = database.execute(self) ^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 3244, in execute return self.execute_sql(sql, params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 3234, in execute_sql with __exception_wrapper__: File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 3010, in __exit__ reraise(new_type, new_type(exc_value, *exc_args), traceback) File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 192, in reraise raise value.with_traceback(tb) File "/builddir/build/BUILD/peewee-3.16.0/peewee.py", line 3236, in execute_sql cursor.execute(sql, params or ()) peewee.OperationalError: database is locked Fssssssss..............................sssssss........sss.......ssssssssssssss.....s........................s.................................. ====================================================================== FAIL: test_multiple_writers (tests.db_tests.TestThreadSafety.test_multiple_writers) ---------------------------------------------------------------------- Traceback (most recent call last): File "/builddir/build/BUILD/peewee-3.16.0/tests/db_tests.py", line 367, in test_multiple_writers self.assertEqual(User.select().count(), self.nrows * self.nthreads) AssertionError: 20 != 40 ``` Full log: https://kojipkgs.fedoraproject.org//work/tasks/6601/99476601/build.log Failing build: https://koji.fedoraproject.org/koji/taskinfo?taskID=99476601 Thank you.

https://api.github.com/repos/coleifer/peewee/issues/2699/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2698

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2698/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2698/comments

https://api.github.com/repos/coleifer/peewee/issues/2698/events

https://github.com/coleifer/peewee/pull/2698

PR_kwDOAA7yGM5M6wfI

Ae configurable default

closed

NONE

## Context Make it so that we can configure the type of the id that is created

https://api.github.com/repos/coleifer/peewee/issues/2698/timeline

https://api.github.com/repos/coleifer/peewee/issues/2697

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2697/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2697/comments

https://api.github.com/repos/coleifer/peewee/issues/2697/events

https://github.com/coleifer/peewee/issues/2697

I_kwDOAA7yGM5hbF-q

peewee-value-returns-to-its-default-after-few-seconds-bug

closed

NONE

https://stackoverflow.com/questions/75804965/peewee-value-returns-to-its-default-after-few-seconds-bug Can you explain this ?

https://api.github.com/repos/coleifer/peewee/issues/2697/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2696

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2696/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2696/comments

https://api.github.com/repos/coleifer/peewee/issues/2696/events

https://github.com/coleifer/peewee/issues/2696

I_kwDOAA7yGM5hZzn3

Point type

closed

NONE

Good afternoon people. Most databases implement the Point type. I've implemented a custom type but I don't know if that's on your roadmap. I would like to implement it natively in PeeWee.

https://api.github.com/repos/coleifer/peewee/issues/2696/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2695

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2695/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2695/comments

https://api.github.com/repos/coleifer/peewee/issues/2695/events

https://github.com/coleifer/peewee/issues/2695

I_kwDOAA7yGM5hKScG

FOR UPDATE not supported by CockroachDatabase

closed

NONE

I believe this is a bug. I am getting the following error when I try to use `for_update()` in Cockroach DB: ``` File "/workspace/nuhom-api/.venv/lib/python3.10/site-packages/peewee.py", line 2509, in __sql__ raise ValueError('FOR UPDATE specified but not supported ' graphql.error.graphql_error.GraphQLError: FOR UPDATE specified but not supported by database. ``` It looks like `CockroachDatabase` believes `FOR UPDATE` is not supported (which may have been the case in an earlier version): https://github.com/coleifer/peewee/blob/b5cee5e99bcc0b20010646cb52c60f8e37dd620a/playhouse/cockroachdb.py#L65 But, in the CockroachDB docs, it states that `FOR UPDATE` is now supported: https://www.cockroachlabs.com/docs/stable/select-for-update.html And, even though CockroachDB does not support [locking strengths](https://www.cockroachlabs.com/docs/v22.2/select-for-update#locking-strengths) (`FOR SHARE` or `FOR KEY SHARE`), the syntax is also supported to be compatible with Postgres.

https://api.github.com/repos/coleifer/peewee/issues/2695/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2694

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2694/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2694/comments

https://api.github.com/repos/coleifer/peewee/issues/2694/events

https://github.com/coleifer/peewee/issues/2694

I_kwDOAA7yGM5hIDkn

`CharField.max_length` has no effect on a Sqlite database

closed

NONE

https://api.github.com/repos/coleifer/peewee/issues/2694/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2693

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2693/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2693/comments

https://api.github.com/repos/coleifer/peewee/issues/2693/events

https://github.com/coleifer/peewee/issues/2693

I_kwDOAA7yGM5hCodA

peewee.ProgrammingError: Error binding parameter 1: type 'builtin_function_or_method' is not supported

closed

NONE

I am trying to update. I get this error. My Code:  Here is the error: Traceback (most recent call last): File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 3236, in execute_sql cursor.execute(sql, params or ()) sqlite3.ProgrammingError: Error binding parameter 1: type 'builtin_function_or_method' is not supported During handling of the above exception, another exception occurred: Traceback (most recent call last): File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\eel\__init__.py", line 318, in _process_message return_val = _exposed_functions[message['name']](*message['args']) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "E:\personal\Shoonya\start.py", line 39, in loginDefault dbHelper.updateLastLogin() File "E:\personal\Shoonya\lib\db.py", line 63, in updateLastLogin Credential.update(last_login=datetime.datetime.now).where(Credential.is_default == True).execute() File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 1962, in inner return method(self, database, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 2033, in execute return self._execute(database) ^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 2551, in _execute cursor = database.execute(self) ^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 3244, in execute return self.execute_sql(sql, params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 3234, in execute_sql with __exception_wrapper__: File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 3010, in __exit__ reraise(new_type, new_type(exc_value, *exc_args), traceback) File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 192, in reraise raise value.with_traceback(tb) File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 3236, in execute_sql cursor.execute(sql, params or ()) peewee.ProgrammingError: Error binding parameter 1: type 'builtin_function_or_method' is not supported Traceback (most recent call last): File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\gevent\_ffi\loop.py", line 270, in python_check_callback def python_check_callback(self, watcher_ptr): # pylint:disable=unused-argument ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 2033, in execute return self._execute(database) ^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 2551, in _execute cursor = database.execute(self) ^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 3244, in execute return self.execute_sql(sql, params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 3234, in execute_sql with __exception_wrapper__: File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 3010, in __exit__ reraise(new_type, new_type(exc_value, *exc_args), traceback) File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 192, in reraise raise value.with_traceback(tb) File "C:\Users\ranjith-15557\AppData\Local\Programs\Python\Python311\Lib\site-packages\peewee.py", line 3236, in execute_sql cursor.execute(sql, params) peewee.ProgrammingError: Error binding parameter 1: type 'builtin_function_or_method' is not supported

https://api.github.com/repos/coleifer/peewee/issues/2693/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2692

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2692/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2692/comments

https://api.github.com/repos/coleifer/peewee/issues/2692/events

https://github.com/coleifer/peewee/issues/2692

I_kwDOAA7yGM5gxfF-

Creating indexes on UUID primary key failes

closed

NONE

During creating of tables and creating indexes on that table it failes to create indexes on UUID key. ## The code ``` python import uuid from playhouse.postgres_ext import UUIDField class CommandControl(Model): id = UUIDField(primary_key=True, default=uuid.uuid4) def migrate(migrator, database, fake=False, **kwargs): """Write your migrations here.""" migrator.create_table(CommandControl) migrator.add_index(CommandControl.id) ``` ## The error ``` bash File "/app/__pypackages__/3.10/lib/peewee_migrate/migrator.py", line 117, in wrapper model._meta.schema = migrator.schema AttributeError: 'UUIDField' object has no attribute '_meta' ```

https://api.github.com/repos/coleifer/peewee/issues/2692/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2691

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2691/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2691/comments

https://api.github.com/repos/coleifer/peewee/issues/2691/events

https://github.com/coleifer/peewee/issues/2691

I_kwDOAA7yGM5ghPT_

reflection.generate_models BinaryJSONField column always has index, even when underlying database schema has no index

closed

NONE

I have a table defined as follows: ```python from playhouse.postgres_ext import BinaryJSONField class MyTable(flask_db.Model): some_data = BinaryJSONField(index=False) ``` For this table, we don’t need an index since we only ever write to this table. When I try to use generate_models on this table, the generated BinaryJSONField has `index=True`, as demonstrated below: ```python from playhouse.reflection import generate_models from models import MyTable generated_model = generate_models(flask_db.database, table_names=["mytable"])["mytable"] generated_column = generated_model._meta.columns["some_data"] reference_column = MyTable._meta.columns["some_data"] # Raises an error: assert generated_column.index == reference_column.index ``` I believe this is happening because `BinaryJSONField` inherits from `IndexedFieldMixin` and, therefore, defaults the `index` parameter to `True`. The reflection code checks for indexes and adds `index=True` to column definitions when necessary to create the corresponding indexes, but does not add `index=False` when they are not required ([see here](https://github.com/coleifer/peewee/blob/3fc96dbe33500d3e5099ea11ef7af080900127ba/playhouse/reflection.py#L762-L767)). That normally works, but not for column types that include `IndexedFieldMixin`. The preferred behavior would be for the `index=False` value to taken into account when creating the table. Would you please take a look? Thank you!

https://api.github.com/repos/coleifer/peewee/issues/2691/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2690

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2690/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2690/comments

https://api.github.com/repos/coleifer/peewee/issues/2690/events

https://github.com/coleifer/peewee/issues/2690

I_kwDOAA7yGM5gfz1E

Prefetch with many ForeignKeyField to same model

closed

NONE

Hello! I'm have 2 models: ``` class State(Entity): uuid = UUIDField(column_name='uuid', primary_key=True) class Transition(Entity): uuid = UUIDField(column_name='uuid', primary_key=True) source_state = ForeignKeyField(State, column_name='source_state_id', backref='_db_source_transitions') target_state = ForeignKeyField(State, column_name='target_state_id', backref='_db_target_transitions') ``` I'm trying load `State` entity and all his `Transition`: ``` states = State.select().where(...) transitions = Transition.select() states = prefetch(states, transitions, prefetch_type=PREFETCH_TYPE.JOIN) ``` I get the following query: ``` SELECT ... FROM "transition" AS "t1" INNER JOIN (SELECT "t2"."uuid", "t2"."uuid" FROM "state" AS "t2" WHERE (...)) AS "t3" ON (("t3"."uuid" = "t1"."source_state_id") OR ("t3"."uuid" = "t1"."target_state_id")) ``` and error in ON statement: ``` column reference "uuid" is ambiguous ``` Is there a way to specify the single foreign key used or is it a bug?

https://api.github.com/repos/coleifer/peewee/issues/2690/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2689

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2689/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2689/comments

https://api.github.com/repos/coleifer/peewee/issues/2689/events

https://github.com/coleifer/peewee/issues/2689

I_kwDOAA7yGM5gYX0T

Is it possible to serialise peewee.Expression?

closed

NONE

it is not an issue, but I didn't find other communication channel to get some ideas in how to serialise peewee.Expression to pass it to the API and later use there as filter in the query. Thanks

https://api.github.com/repos/coleifer/peewee/issues/2689/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2688

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2688/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2688/comments

https://api.github.com/repos/coleifer/peewee/issues/2688/events

https://github.com/coleifer/peewee/pull/2688

PR_kwDOAA7yGM5LWNxs

mysql add column comment

closed

NONE

mysql add column comment with verbose_name or help_text

https://api.github.com/repos/coleifer/peewee/issues/2688/timeline

https://api.github.com/repos/coleifer/peewee/issues/2687

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2687/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2687/comments

https://api.github.com/repos/coleifer/peewee/issues/2687/events

https://github.com/coleifer/peewee/issues/2687

I_kwDOAA7yGM5f-EE0

`playhouse.signals.Signal.disconnect` disconnects more than key, sender pair.

closed

NONE

When connecting two receiver to the same sender and disconnecting one of them. Both are disconnected. This bug is also illustrated by the code itself: https://github.com/coleifer/peewee/blob/f88fa44a29601ca2de9fe492fda11b1fb28fb412/playhouse/signals.py#L25-L38 The `_receivers` set stores pairs of receiver and model. When disconnecting a single pair is removed if present. However `_receiver_list` looses all entries for which `n != name and s != sender` is false. Quick transformation: $$ \lnot( n \ne name \land s \ne sender ) \Leftrightarrow $$ $$ \lnot( n \ne name ) \lor \lnot( s \ne sender ) \Leftrightarrow $$ $$ n = name \lor s = sender $$ Notice that all receivers are removed that have a matching name or receiver.

https://api.github.com/repos/coleifer/peewee/issues/2687/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2686

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2686/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2686/comments

https://api.github.com/repos/coleifer/peewee/issues/2686/events

https://github.com/coleifer/peewee/issues/2686

I_kwDOAA7yGM5f-CWw

Undocumented parameter `sender` for `playhouse.signals.Signal.disconnect`.

closed

NONE

https://github.com/coleifer/peewee/blob/f88fa44a29601ca2de9fe492fda11b1fb28fb412/playhouse/signals.py#L25 There is a `sender` parameter. However there is no such parameter here: https://github.com/coleifer/peewee/blob/f88fa44a29601ca2de9fe492fda11b1fb28fb412/docs/peewee/playhouse.rst?plain=1#L2740

https://api.github.com/repos/coleifer/peewee/issues/2686/timeline

not_planned

https://api.github.com/repos/coleifer/peewee/issues/2685

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2685/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2685/comments

https://api.github.com/repos/coleifer/peewee/issues/2685/events

https://github.com/coleifer/peewee/issues/2685

I_kwDOAA7yGM5f7VPS

Cast Bigint to timestamp

closed

NONE

Hello, I am trying to partition some data using `fn.date_part` on a `TimestampField`. Here is my simplified model: ``` class Game(Model): id = PrimaryKeyField() ts_played = TimestampField(utc=True, default=None, null=True) score = IntegerField(null=True) ``` My full query: ``` results = Game \ .select( fn.date_part("week", Game.ts_played).alias("week"), fn.SUM(Game.score).alias("total_score") ) \ .where( Game.ts_played.is_null(False), Game.score.is_null(False), Game.ts_played >= 123456789, Game.ts_played <= 987654321 ) \ .group_by(fn.date_part("week", Game.ts_played)) \ .order_by(fn.date_part("week", Game.ts_played)) ``` I get the following error: ``` peewee.ProgrammingError: function date_part(unknown, bigint) does not exist ``` which does not surprise me because TimestampField is not really a timestamp but rather a Bigint. I then try to cast the underlying bigint to timestamp, replacing `Game.ts_played` everywhere in the query above with: ``` Game.ts_played.cast("timestamp") ``` I get the error ``` peewee.ProgrammingError: cannot cast type bigint to timestamp without time zone ``` It works fine without casting when I change `ts_played` to be a `DateTimeField`. Is there a convenient way to partition a `TimestampField` in weeks?

https://api.github.com/repos/coleifer/peewee/issues/2685/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2684

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2684/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2684/comments

https://api.github.com/repos/coleifer/peewee/issues/2684/events

https://github.com/coleifer/peewee/issues/2684

I_kwDOAA7yGM5fd0sS

Build failures with Cython 3.0.0b1

closed

NONE

Cython 3.0.0 has released its first beta, meaning that 3.0.0 final will be out sooner than later. Right now peewee fails to build with it: ``` $ python setup.py build Compiling playhouse/_sqlite_udf.pyx because it changed. Compiling playhouse/_sqlite_ext.pyx because it changed. [1/2] Cythonizing playhouse/_sqlite_ext.pyx /tmp/peewee/venv/lib/python3.11/site-packages/Cython/Compiler/Main.py:370: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /tmp/peewee/playhouse/_sqlite_ext.pyx tree = Parsing.p_module(s, pxd, full_module_name) Error compiling Cython file: ------------------------------------------------------------ ... pIdxInfo.estimatedCost = <double>1 pIdxInfo.estimatedRows = 10 else: # Penalize score based on number of missing params. pIdxInfo.estimatedCost = <double>10000000000000 * <double>(nParams - nArg) pIdxInfo.estimatedRows = 10 ** (nParams - nArg) ^ ------------------------------------------------------------ playhouse/_sqlite_ext.pyx:608:40: Cannot assign type 'double' to 'sqlite3_int64' Error compiling Cython file: ------------------------------------------------------------ ... self._commit_hook = fn if fn is None: sqlite3_commit_hook(self.conn.db, NULL, NULL) else: sqlite3_commit_hook(self.conn.db, _commit_callback, <void *>fn) ^ ------------------------------------------------------------ playhouse/_sqlite_ext.pyx:1463:46: Cannot assign type 'int (void *) except? -1 nogil' to 'int (*)(void *) noexcept nogil' Error compiling Cython file: ------------------------------------------------------------ ... self._rollback_hook = fn if fn is None: sqlite3_rollback_hook(self.conn.db, NULL, NULL) else: sqlite3_rollback_hook(self.conn.db, _rollback_callback, <void *>fn) ^ ------------------------------------------------------------ playhouse/_sqlite_ext.pyx:1473:48: Cannot assign type 'void (void *) except * nogil' to 'void (*)(void *) noexcept nogil' Error compiling Cython file: ------------------------------------------------------------ ... self._update_hook = fn if fn is None: sqlite3_update_hook(self.conn.db, NULL, NULL) else: sqlite3_update_hook(self.conn.db, _update_callback, <void *>fn) ^ ------------------------------------------------------------ playhouse/_sqlite_ext.pyx:1483:46: Cannot assign type 'void (void *, int, const char *, const char *, sqlite3_int64) except * nogil' to 'void (*)(void *, int, char *, char *, sqlite3_int64) noexcept nogil' Error compiling Cython file: ------------------------------------------------------------ ... """ if not self.conn.initialized or not self.conn.db: return False cdef sqlite3_int64 n = timeout * 1000 sqlite3_busy_handler(self.conn.db, _aggressive_busy_handler, <void *>n) ^ ------------------------------------------------------------ playhouse/_sqlite_ext.pyx:1494:43: Cannot assign type 'int (void *, int) except? -1 nogil' to 'int (*)(void *, int) noexcept nogil' Traceback (most recent call last): File "/tmp/peewee/setup.py", line 185, in <module> _do_setup(extension_support, sqlite_extension_support) File "/tmp/peewee/setup.py", line 180, in _do_setup ext_modules=cythonize(ext_modules)) ^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/peewee/venv/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1134, in cythonize cythonize_one(*args) File "/tmp/peewee/venv/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1301, in cythonize_one raise CompileError(None, pyx_file) Cython.Compiler.Errors.CompileError: playhouse/_sqlite_ext.pyx ``` To reproduce: ``` pip install Cython==3.0.0b1 python setup.py build ```

https://api.github.com/repos/coleifer/peewee/issues/2684/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2683

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2683/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2683/comments

https://api.github.com/repos/coleifer/peewee/issues/2683/events

https://github.com/coleifer/peewee/issues/2683

I_kwDOAA7yGM5fXFoE

Can't query with unicode character

closed

NONE

I have a column containing this type of data `{"zh": "\u65e5\u97e9\u5267"}` and when I query it with this code `Video.select().where(Video.director.contains('\u65e5\u97e9\u5267'))` , I'm not getting any result. It only works when I query non-unicode text e.g. `Video.select().where(Video.director.contains('"zh"'))`.

https://api.github.com/repos/coleifer/peewee/issues/2683/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2682

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2682/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2682/comments

https://api.github.com/repos/coleifer/peewee/issues/2682/events

https://github.com/coleifer/peewee/issues/2682

I_kwDOAA7yGM5fW-zt

peewee.InterfaceError: Error, database must be initialized before opening a connection.

closed

NONE

import os from playhouse.postgres_ext import CharField, DateTimeField, IntegerField, BooleanField from .base import Base import datetime from peewee import PostgresqlDatabase from playhouse.migrate import * db_name = os.environ.get('DB_NAME') db_host = os.environ.get('DB_HOST') db_port = os.environ.get('DB_PORT') db_password = os.environ.get('DB_PASSWORD') db_user= os.environ.get('DB_USER') # Initialize database. pg_db = PostgresqlExtDatabase(db_name, user=db_user, password=db_password,host=db_host, port=db_port) migrator = PostgresqlMigrator(pg_db) class EmpDetails(Base): id = CharField(25, null=False) email = CharField(255, unique=True) name = CharField(255) location = CharField(255) created_at = DateTimeField(default=datetime.datetime.now) updated_at = DateTimeField(default=datetime.datetime.now) is_active = BooleanField(default=True) role = CharField(25) class Meta: table_name = 'emp_details' test_field = CharField(default='') migrate( migrator.add_column('emp_details', 'test', test_field), ) I'm trying to make my DB instance for migration but getting an error : ``` File "/home/naveen.p@ah.zymrinc.com/Desktop/zfr/server/s-venv/lib/python3.8/site-packages/peewee.py", line 3026, in connect raise InterfaceError('Error, database must be initialized ' peewee.InterfaceError: Error, database must be initialized before opening a connection. ```

https://api.github.com/repos/coleifer/peewee/issues/2682/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2681

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2681/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2681/comments

https://api.github.com/repos/coleifer/peewee/issues/2681/events

https://github.com/coleifer/peewee/issues/2681

I_kwDOAA7yGM5fU7mA

Does migrate() run every time I run server(Ex. flask server)

closed

NONE

Suppose I've added create_table(fail_silently=True) when the flask server starts. In this model class below, I want to add the column "test" in my DB corresponding field "test_field". Question: 1. Do I need to add "test_field" in my model **EmpDetails** or outside the **class** or both(like I did in the code snippet) for migrations? 2. As I've created create_function() to run at the server(flask server) start, will it migrate() every time at the start of the server(_I need to make sure whether data added in the new column will not vanish if migrate runs every time_). or if the schema changes are done in the database will it not rerun the migration? Code snippet for my model class: ``` class EmpDetails(Base): id = CharField(25, null=False) email = CharField(255, unique=True) name = CharField(255) location = CharField(255) created_at = DateTimeField(default=datetime.datetime.now) updated_at = DateTimeField(default=datetime.datetime.now) is_active = BooleanField(default=True) role = CharField(25) test_field = CharField(default='') -------> here class Meta: table_name = 'emp_details' test_field = CharField(default='') ---------> here migrate( migrator.add_column(EmpDetails._meta.emp_details, 'test', test_field), ) ```

https://api.github.com/repos/coleifer/peewee/issues/2681/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2680

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2680/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2680/comments

https://api.github.com/repos/coleifer/peewee/issues/2680/events

https://github.com/coleifer/peewee/issues/2680

I_kwDOAA7yGM5e9-CH

How to use with pgbouncer?

closed

NONE

Could someone, please, make clear, how to use peewee with pgbouncer? Am I supposed to use `PooledPostgresqlExtDatabase` or it's overkill and just `PostgresqlExtDatabase` will be fine? Connection string will point to pgbouncer.

https://api.github.com/repos/coleifer/peewee/issues/2680/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2679

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2679/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2679/comments

https://api.github.com/repos/coleifer/peewee/issues/2679/events

https://github.com/coleifer/peewee/pull/2679

PR_kwDOAA7yGM5KXb30

Fix typo in docs

closed

NONE

https://api.github.com/repos/coleifer/peewee/issues/2679/timeline

https://api.github.com/repos/coleifer/peewee/issues/2678

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2678/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2678/comments

https://api.github.com/repos/coleifer/peewee/issues/2678/events

https://github.com/coleifer/peewee/issues/2678

I_kwDOAA7yGM5enRWu

Playhouse Migrator does not honour model schema

closed

NONE

Sorry for not including a full code example: I'm using playhouse.migrate in a utility and it would be more than overkill to include all of it, not to mention it's closed-source company code I'm not allowed to share. But I believe there's enough information to tackle the issue. In all the scenarios below, I call `migrate(*actions)` where `actions = [migrator.add_column(table_name, "fieldname", TextField(default=""))]` or similar. `table_name` is always `MyPeeweeModel._meta.table_name` and the model always has `Meta.schema` set to a constant value. Note that I'm using Postgresql (both for the database and the migrator, obviously). Note: if I want to create the table for my model it seems my only options are either raw SQL or `database.create_tables()`. Setting aside the fact that I don't want to use the latter because it creates fields for the *current* state of the model, which isn't what I want, if I do use it, it **does** create the table in the correct schema. Further note: there seems to be no way to create the schema itself, so I resorted to doing this manually. I can't remember if `.create_tables()` attemps doing it at all but as I said, I need to bypass that and create the table manually to prevent inconsistencies between the table's initial state and any migrations. **Scenario 1:** I attempt: ```python migrate( # table_name is simply MyPeeweeModel._meta.table_name migrator.add_column(table_name, "fieldname", TextField(default="")), ) ``` *Result:* "peewee.ProgrammingError: relation "mytable" does not exist". The table *does* exist in the database at that point, so I must surmise that the schema is not prepended to the path to the table; in other words Peewee looks for the table without honouring the schema. **Scenario 2:** I attempt: ```python migrate( # table_name is a string like schema.table where the schema comes from MyPeeweeModel._meta.schema migrator.add_column(table_name, "fieldname", TextField(default="")), ) ``` *Result:* "peewee.ProgrammingError: relation "myschema.mytable" does not exist". Again, the table actually exists in the right schema. The relation which isn't found is incorrectly quoted, because it enquotes myschema.mytable entirely instead of the schema and the table separately. **Scenario 3:** I attempt: ```python migrate( # table_name is a pre-quoted string like "schema"."table" migrator.add_column(table_name, "fieldname", TextField(default="")), ) ``` *Result:* "peewee.ProgrammingError: relation ""myschema"."mytable"" does not exist". Same as above: the whole thing is quoted regardless of the fact that the identifiers are already quoted. **Scenario 4:** As I traced back the quoting Peewee does to the `Entity` class and I noticed its init: ```python def __init__(self, *path): self._path = [part.replace('"', '""') for part in path if part] ``` takes an iterable, I tried giving it a tuple like `(schema, table)` but that didn't work, and if I try to place a breakpoint in the init, my debugger crashes every time while trying to collect data (presumably on `self`'s attributes), even if I monkeypatch the whole function (!). As such, I'm quite stuck and am also unable to open a pull request to fix the issue myself, since debugging it seems nigh on impossible. I'm honestly surprised this hasn't come up before: has nobody ever tested or tried to use the migration helpers with a non-default schema?

https://api.github.com/repos/coleifer/peewee/issues/2678/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2677

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2677/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2677/comments

https://api.github.com/repos/coleifer/peewee/issues/2677/events

https://github.com/coleifer/peewee/pull/2677

PR_kwDOAA7yGM5JmIK6

query.first() mutates the query

closed

CONTRIBUTOR

The `query.first()` method mutates the query and it may lead to unexpected behaviour ```python query = SomeModel.select() first_item = query.first() for item in query: # This cycle only runs once, because after first() the query is mutated and now it has limit 1 ``` The PR fixes the behaviour.

https://api.github.com/repos/coleifer/peewee/issues/2677/timeline

https://api.github.com/repos/coleifer/peewee/issues/2676

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2676/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2676/comments

https://api.github.com/repos/coleifer/peewee/issues/2676/events

https://github.com/coleifer/peewee/pull/2676

PR_kwDOAA7yGM5JlA0X

merge latest dev

closed

NONE

void

https://api.github.com/repos/coleifer/peewee/issues/2676/timeline

https://api.github.com/repos/coleifer/peewee/issues/2675

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2675/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2675/comments

https://api.github.com/repos/coleifer/peewee/issues/2675/events

https://github.com/coleifer/peewee/issues/2675

I_kwDOAA7yGM5d7KWI

excuse, how could i use a variable as table's field

closed

NONE

eg: create table test ( id int auto_increment primary key, name varchar(255) null, ); field = 'name' query_list = list(test.select().where(test.field=='cc').dicts()) AttributeError: type object 'test' has no attribute 'field' want to know the api

https://api.github.com/repos/coleifer/peewee/issues/2675/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2674

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2674/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2674/comments

https://api.github.com/repos/coleifer/peewee/issues/2674/events

https://github.com/coleifer/peewee/issues/2674

I_kwDOAA7yGM5d32x1

Example of custom operators for custom fields?

closed

NONE

I've tried to find an instance of a custom field that needed to override the behavior of something like the `+` operator but haven't found one. As an example scenario, let's say I had a custom field named `CounterDictField` (that subclassed `JSONField` for storage). I want to override the `__add__` method in the `CounterDictField` class with code that behaves like this: ```python # override '+' operator to numerically add together dictionary values with the same key def __add__(lhs, rhs): return {key: lhs.get(key, 0) + rhs.get(key, 0) for key in set(lhs).union(rhs)} ``` so `+` _numerically sums_ the entries of the two dictionaries: ```python stats = {"a": 1, "b": 2, "c": 3} new_stats = {"b": -1, "d": 1} stats = __add__(stats, new_stats) # stats={'c': 3, 'd': 1, 'a': 1, 'b': 1} # 'stats' now contains the result of numerically summing the values with matching keys in 'new_stats' ``` This is so that I can make an "upsert" call (where the `stats` column is the above `CounterDictField` field type): ```python MyTable.insert(user_id=user_id, username=username, stats=stats). on_conflict( conflict_target=[MyTable.user_id], preserve=[MyTable.username], update={MyTable.stats: MyTable.stats + stats} ).execute() ``` and have the `stats` field _add to_ existing stats in the dict for records that already exist. Is something like this possible?

https://api.github.com/repos/coleifer/peewee/issues/2674/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2673

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2673/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2673/comments

https://api.github.com/repos/coleifer/peewee/issues/2673/events

https://github.com/coleifer/peewee/issues/2673

I_kwDOAA7yGM5d0DPs

MySQL introspector returns columns in non-deterministic order

closed

NONE

When I use the introspector to generate model classes for MySQL tables, the order of columns seems non-deterministic. It turns out that `MySQLDatabase.get_columns()` does not fetch columns ordered by their ordinal position. (Sometimes the columns are simply returned alphabetically, from what I observed.) Could we add `ORDER BY ordinal_position` when selecting from the `information_schema.columns` table in MySQL? Here is the code for MySQL, and there is no `ORDER BY` clause: https://github.com/coleifer/peewee/blob/e4f5df28e1b3716de1c006652371744da3743018/peewee.py#L4193-L4197 We can see that for PostgreSQL, columns are returned in a deterministic order: https://github.com/coleifer/peewee/blob/e4f5df28e1b3716de1c006652371744da3743018/peewee.py#L3983-L3988

https://api.github.com/repos/coleifer/peewee/issues/2673/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2672

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2672/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2672/comments

https://api.github.com/repos/coleifer/peewee/issues/2672/events

https://github.com/coleifer/peewee/issues/2672

I_kwDOAA7yGM5dGMzp

migrator may conflict with AutoIncrementField in sqlite

closed

NONE

I have created a sqlite table 'user' using peewee: The table generally looks like this: > id name > 1 name1 > 2 name2 > 3 name3 > 4 name4 (deleted) For column id, i'm using `AutoIncrementField` from `playhouse.sqlite_ext` to prevent the deleted id from being reused Since the name4 line has been deleted, the id of next created user should be 5 Then i used a migrator to remove the not-null constraint on field name `migrator = SqliteMigrator(database)` `migrator.drop_not_null('user', 'name')` But after this i created a user and the id field was 4, the deleted id was still reused Without `migrator.drop_not_null('user', 'name')`, the id column works as expected

https://api.github.com/repos/coleifer/peewee/issues/2672/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2671

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2671/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2671/comments

https://api.github.com/repos/coleifer/peewee/issues/2671/events

https://github.com/coleifer/peewee/issues/2671

I_kwDOAA7yGM5czoCa

Value not saved when an alias (column_name) used

closed

NONE

``` >>> class Test(BaseModel): ... test1 = DecimalField(constraints=[SQL("DEFAULT 0.00")], null=True) ... class Meta: ... table_name = 'test' ... >>> >>> >>> Test.create_table() >>> Test.insert(test1=12).execute() 1 >>> a=Test[1] >>> a.test1=20; >>> a.save() 1 >>> a=Test[1] >>> a.test1 Decimal('20.00000') ``` Up to now, normal, correct. Lets define an alias (2nd field) for test1 field: ``` class Test(BaseModel): test1 = DecimalField(constraints=[SQL("DEFAULT 0.00")], null=True) test2 = DecimalField(constraints=[SQL("DEFAULT 0.00")], null=True, column_name='test1') class Meta: table_name = 'test' >>> a=Test[1] >>> a.test1=30 >>> a.save() 0 >>> ``` So, that entity unchanged. I am not sure if this is an intended behaviour, but, it is obviously misleading. I encountered this during dealing with a bug and this was the issue. it was not saving the value.

https://api.github.com/repos/coleifer/peewee/issues/2671/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2670

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2670/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2670/comments

https://api.github.com/repos/coleifer/peewee/issues/2670/events

https://github.com/coleifer/peewee/issues/2670

I_kwDOAA7yGM5cjf7R

[Feature Request] Event hooks for peewee

closed

NONE

For now, I'm looking for event hooks in peewee, but I think we don't support event hooks for peewee yet(I have already read the docs, please feel free to correct me if I'm wrong) I think it's an excellent choice to support event hooks like Django ORM or sqlalchemy like below. ```python from peewee import event event.listen(client, "before_cursor_execute", callback_func) ``` The code above means that the callback function will be executed before the final SQL start to be executed. It's a good feature for a lot of people. For example, we can inject the trace ID in SQL by using SQL comment using https://google.github.io/sqlcommenter/python/sqlalchemy/ FYI https://docs.sqlalchemy.org/en/14/core/events.html

https://api.github.com/repos/coleifer/peewee/issues/2670/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2669

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2669/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2669/comments

https://api.github.com/repos/coleifer/peewee/issues/2669/events

https://github.com/coleifer/peewee/issues/2669

I_kwDOAA7yGM5cf-yc

How to use instance-relative SQLite databases with FlaskDB

closed

NONE

I have this code in `test/__init__.py`: ```python import os import contextlib from flask import Flask from peewee import CharField, PrimaryKeyField from playhouse.flask_utils import FlaskDB db_wrapper = FlaskDB() class User(db_wrapper.Model): user_id = PrimaryKeyField() user_name = CharField(max_length=128, unique=True) def create_app() -> Flask: app = Flask(__name__, instance_relative_config=True) app.config.from_mapping( DATABASE="sqlite://" + os.path.join(app.instance_path, "db.sqlite"), # DATABASE="sqlite:///db.sqlite", ) # create instance path if it doesn't already exist with contextlib.suppress(OSError): os.makedirs(app.instance_path) db_wrapper.init_app(app) if db := db_wrapper.database: db.create_tables([User], safe=True) return app ``` and when I run: ```shell flask --app test --debug run ``` It errors with: ```text peewee.OperationalError: unable to open database file ``` *__but__* if I uncomment the `DATABASE` line shown above so it _doesn't_ use `app.instance_path`, it works fine (but then the database isn't in the `instance` directory). The `app.instance_path` does exist (or gets created by the code if it's missing). FWIW, if I replace the call to `db.create_tables` with `db.connect()` _(for example)_ I get the same error. Is there something I'm missing with getting the SQLite database into the `instance_path` directory?

https://api.github.com/repos/coleifer/peewee/issues/2669/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2668

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2668/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2668/comments

https://api.github.com/repos/coleifer/peewee/issues/2668/events

https://github.com/coleifer/peewee/issues/2668

I_kwDOAA7yGM5bYv4I

The record is not saving in only one Table

closed

NONE

Only the "c" part is saved, although I do exactly the same thing, the "u" part changes, but it is not saved in the database. When I put .save (force_insert) it gives an error: `UNIQUE constraint failed: Users.id` Code(3 files): ``` # main.py # self.event.text.lower()[15:] - user id # self.db - current user database c = utils.getClanById(self.db.userId) c.users = c.users.replace(f"{self.event.text.lower()[15:]}/", "") c.save() u = utils.getUserById(int(self.event.text.lower()[15:])) u.user_clan = "" u.save() # utils.py import time from models import * def getUserById(user_id): try: return User().get(User.userId == user_id) except: User( userId=user_id, name="", lastTimeUsedBonus=time.time() - 86400, money=0, GB=0, crowns=0, place=1000, user_clan="", clan_invites="" ).save() return User().get(vk_id=user_id) def getClanById(user_id, buy=False): user_id = int(user_id) try: return Clan().get(Clan.owner_id == user_id) except: if buy: Clan( owner_id=user_id, name="", idd=0, users="", base=1, rating=0, coffers=0, wins=0, loses=0 ).save() return Clan().get(Clan.owner_id == user_id) # models.py from peewee import * dbu = SqliteDatabase('users and clans.db') class User(Model): class Meta: database = dbu db_table = 'Users' userId = IntegerField() name = TextField() lastTimeUsedBonus = TimeField() money = IntegerField() GB = IntegerField() crowns = IntegerField() user_clan = TextField() clan_invites = TextField() class Clan(Model): class Meta: database = dbu db_table = 'Clans' owner_id = IntegerField() name = TextField() idd = IntegerField() users = TextField() base = IntegerField() rating = IntegerField() coffers = IntegerField() wins = IntegerField() loses = IntegerField() if __name__ == '__main__': dbu.create_tables([Clan, User]) ```

https://api.github.com/repos/coleifer/peewee/issues/2668/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2667

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2667/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2667/comments

https://api.github.com/repos/coleifer/peewee/issues/2667/events

https://github.com/coleifer/peewee/issues/2667

I_kwDOAA7yGM5bYhxh

OSS License compatibility question

closed

NONE

There’s some possible confusion on the license of your repository when you combine other open-source code. The module `tests/libs/mock.py` claims its license as **the BSD License**. However, the license of your whole project is shown as **the MIT license** in LICENSE, i.e., **less strict** than the BSD License on license terms, which has impacted the whole license compatibility in your repository and may bring legal and financial risks. You can select another proper license for your repository, or write a custom license with license exceptions if some license terms couldn’t be summed up consistently

https://api.github.com/repos/coleifer/peewee/issues/2667/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2666

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2666/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2666/comments

https://api.github.com/repos/coleifer/peewee/issues/2666/events

https://github.com/coleifer/peewee/issues/2666

I_kwDOAA7yGM5bQC-1

Closing SQLite3 db blocks

closed

NONE

hi, I am writing a Kodi addon where I wanted to use peewee as my CRM. My Kodi build uses python3.8 internally. I packaged the latest peewee version available and it works fine. I can create databases write to them read from them etc. But if I try to call close() on the database, it blocks forever and the code never exits. The same code runs fine with my PC's python interpreter. The code: https://pastebin.com/zCNreHF0 I tried to debug this. First I tried to create a simple file and close it. That worked just fine. Then I used sqlite3 to create a database, insert a record and close the database. Worked also fine. Then I was suspecting threading.RLock() as the causer, but that also works just fine. Any idea what could be wrong? Can I force the lib to use sqlite3?

https://api.github.com/repos/coleifer/peewee/issues/2666/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2665

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2665/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2665/comments

https://api.github.com/repos/coleifer/peewee/issues/2665/events

https://github.com/coleifer/peewee/issues/2665

I_kwDOAA7yGM5ah1lB

Unable to import module 'app': No module named 'playhouse'

closed

NONE

Hello, I am working on an [AWS Chalice](https://aws.github.io/chalice/quickstart.html#deploying) project, and I chose peewee as the ORM for the postgresql DB we have. When I run things locally with `chalice local` I can run my api with no problem, I'm able to CRUD normally. When I deploy my microservice using `chalice deploy` and I go test it out I encounter an error 500. When looking into the logs I see this message multiple times: ``` Traceback (most recent call last): 2023-01-03 22:39:57.665000 d87bac [ERROR] Runtime.ImportModuleError: Unable to import module 'app': No module named 'playhouse' ``` I cannot do `poetry add playhouse`, because I get the following error: `Could not find a matching version of package playhouse`. What can you suggest me to do to fix this? Thank you so much

https://api.github.com/repos/coleifer/peewee/issues/2665/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2664

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2664/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2664/comments

https://api.github.com/repos/coleifer/peewee/issues/2664/events

https://github.com/coleifer/peewee/issues/2664

I_kwDOAA7yGM5aOG3A

Error when aurora cluster instance failover

closed

NONE

Hi, I'm using PostgresqlDatabase to manage my Aurora DB. I've encountered the following error after the the AZ on which the writer instance went down and caused a failover. ``` Traceback (most recent call last): File "/Users/schmil/work/oxeye-cloud/data_pipeline/sink_instance_creator/sink_instance_persistant_storage.py", line 72, in _handle query.execute() File "/usr/local/lib/python3.9/site-packages/peewee.py", line 1911, in inner return method(self, database, *args, **kwargs) File "/usr/local/lib/python3.9/site-packages/peewee.py", line 1982, in execute return self._execute(database) File "/usr/local/lib/python3.9/site-packages/peewee.py", line 2761, in _execute return super(Insert, self)._execute(database) File "/usr/local/lib/python3.9/site-packages/peewee.py", line 2477, in _execute cursor = self.execute_returning(database) File "/usr/local/lib/python3.9/site-packages/peewee.py", line 2484, in execute_returning cursor = database.execute(self) File "/usr/local/lib/python3.9/site-packages/peewee.py", line 3173, in execute return self.execute_sql(sql, params, commit=commit) File "/usr/local/lib/python3.9/site-packages/peewee.py", line 3167, in execute_sql self.commit() File "/usr/local/lib/python3.9/site-packages/peewee.py", line 2933, in __exit__ reraise(new_type, new_type(exc_value, *exc_args), traceback) File "/usr/local/lib/python3.9/site-packages/peewee.py", line 191, in reraise raise value.with_traceback(tb) File "/usr/local/lib/python3.9/site-packages/peewee.py", line 3158, in execute_sql cursor = self.cursor(commit) File "/usr/local/lib/python3.9/site-packages/peewee.py", line 3145, in cursor return self._state.conn.cursor() peewee.InterfaceError: connection already closed ``` I managed to reproduce it and when checked the connection before executing the query using `is_closed()` it returned false but still got the error I'm using a single connection without connection pool because I have only a single thread How can configure peewee to handle failovers?

https://api.github.com/repos/coleifer/peewee/issues/2664/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2663

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2663/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2663/comments

https://api.github.com/repos/coleifer/peewee/issues/2663/events

https://github.com/coleifer/peewee/issues/2663

I_kwDOAA7yGM5aGnbZ

Suggestion: .is_ and .is_not query lookups

closed

NONE

It'd be great to have an option to write `is` and `is not` lookups via functions `Model.field.is_(value)` and not `Model.field >> value` which is unreadable, similar to `Model.field.in_(value)`. It's useful for writing queries against nullable boolean fields, like `Model.is_finished.is_not(True)` I can submit a pr if you want that change too.

https://api.github.com/repos/coleifer/peewee/issues/2663/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2662

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2662/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2662/comments

https://api.github.com/repos/coleifer/peewee/issues/2662/events

https://github.com/coleifer/peewee/issues/2662

I_kwDOAA7yGM5aEL7u

Suggestion: SQLiteDatabase option to disable automatic DB creation

closed

NONE

There does not appear to be a way to disable DB creation if not found. e.g db = SqliteDatabase('mydb.db', pragmas={'foreign_keys': 1}, **create_db=False**) Why this could be helpful: I just went down a rabbit hole moving running code to an Apache server where I forgot to set **home=/var/www/myapp** in my apache .conf file. The result was everything ran fine without errors but the DB in the same dir as the rest of the code was not found so an empty copy was created by Peewee in /home/<user> This led to troubleshooting why a fully functional db was not returning any data. In most cases of deployment or migration the database should not NEED be 'created' and preventing it from happening iwould immediately show up as an error as it should.

https://api.github.com/repos/coleifer/peewee/issues/2662/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2661

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2661/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2661/comments

https://api.github.com/repos/coleifer/peewee/issues/2661/events

https://github.com/coleifer/peewee/issues/2661

I_kwDOAA7yGM5ZjB7e

bulk_create() doesn't work with server-side default values

closed

NONE

It appears that bulk_create does not work with server-side default values specified in [constraint](https://docs.peewee-orm.com/en/latest/peewee/models.html?highlight=table%20generation#:~:text=can%20use%20the-,constraints,-parameter%20to%20specify). For example, with this model: ``` class MyModel(Modell): datetime = DateTimeField(constraints=[SQL("DEFAULT CURRENT_TIMESTAMP")]) class Meta: database = my_postgresql_db ``` The following works: `MyModel().save()` whereas this fails: ``` MyModel.bulk_create([MyModel()]) # IntegrityError: null value in column "datetime" violates not-null constraint DETAIL: Failing row contains (2, null). ``` Any suggestions on how to bulk create using server-side defaults?

https://api.github.com/repos/coleifer/peewee/issues/2661/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2660

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2660/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2660/comments

https://api.github.com/repos/coleifer/peewee/issues/2660/events

https://github.com/coleifer/peewee/issues/2660

I_kwDOAA7yGM5ZbTOm

playhouse/_sqlite_udf.pyx: compilation error

closed

NONE

Peewee Version: 3.15.4 Python: 3.11.0 Cython: 3.0.0a11 Platform: MacOS M1 - arm64 How to reproduce: pip install peewee ``` Error compiling Cython file: ------------------------------------------------------------ ... if self.ct == 0: return None elif self.ct < 3: return self.items[0] else: return self.selectKth(self.ct / 2) ^ ------------------------------------------------------------ playhouse/_sqlite_udf.pyx:137:42: Cannot assign type 'double' to 'int' ```

https://api.github.com/repos/coleifer/peewee/issues/2660/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2659

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2659/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2659/comments

https://api.github.com/repos/coleifer/peewee/issues/2659/events

https://github.com/coleifer/peewee/issues/2659

I_kwDOAA7yGM5YvNjR

Type support

closed

NONE

Type support in VSCode would be nice. 

https://api.github.com/repos/coleifer/peewee/issues/2659/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2658

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2658/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2658/comments

https://api.github.com/repos/coleifer/peewee/issues/2658/events

https://github.com/coleifer/peewee/issues/2658

I_kwDOAA7yGM5X0Ypf

Gotcha for folks using update

closed

NONE

Speaking from recent experience, I made a mistake when attempting to update a single field on a model. ```python flag = Flag.get_by_id(flag_id) flag.update(active=False).execute() ``` Given that I was operating on an instance of the model, I assumed I'd be updating that field only on a single row. However, given that in Python you can call a classmethod on an instance variable, it updates ALL the flags in the database! I'm glad I wasn't using the delete classmethod by accident. ```python class Test: @classmethod def hello(cls): print("CLASS HELLO") if __name__ == '__main__': t = Test() t.hello() Test.hello() ``` I wish I had a good suggestion for how to help others not make this mistake (other than learning Python better 😢 ). I see you do have `flag.delete_instance()` in addition to `Flag.delete()`. Would an `update_instance` method help? Unfortunately, I see no way to detect, from a classmethod call, whether it was the class or an instance that invoked it. [update] I would favor what you suggested back in 2015: >Classmethods operate on the table. Instance methods operate on the rows. Class represents table, instance represents row. It is just an inconvenient fact of python's `classmethod` decorator that you can call classmethods from an instance. I could write a special decorator that prevented this, e.g. `classonlymethod` but I don't think it's worth the time and more Pythonic anyways. _Originally posted by @coleifer in https://github.com/coleifer/peewee/issues/586#issuecomment-95960454_

https://api.github.com/repos/coleifer/peewee/issues/2658/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2657

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2657/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2657/comments

https://api.github.com/repos/coleifer/peewee/issues/2657/events

https://github.com/coleifer/peewee/issues/2657

I_kwDOAA7yGM5XwRaD

[feature] Query tagging capability

closed

NONE

Hi @coleifer, What do you think in general about providing a capability to add [tags for queries](https://cloud.google.com/sql/docs/postgres/using-query-insights#using-sqlcommenter:~:text=When%20you%20examine%20results%20in%20SQL%20database%20logs%2C%20they%20appear%20as%20follows)? Tagging SQL queries simplifies application troubleshooting and can be helpful for people who are using the Google Cloud SQL. Their Query Insights feature is able to parse tags and provide [application centric view](https://www.youtube.com/watch?v=qN7x3ngwz1o) to SRE.

https://api.github.com/repos/coleifer/peewee/issues/2657/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2656

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2656/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2656/comments

https://api.github.com/repos/coleifer/peewee/issues/2656/events

https://github.com/coleifer/peewee/issues/2656

I_kwDOAA7yGM5Xkjx7

can't select self-children items

closed

NONE

``` Python class A(BaseModel): parent = ForieginField('self', null=True, backref='children') for item in A.select(): print(item.children) ```

https://api.github.com/repos/coleifer/peewee/issues/2656/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2655

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2655/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2655/comments

https://api.github.com/repos/coleifer/peewee/issues/2655/events

https://github.com/coleifer/peewee/issues/2655

I_kwDOAA7yGM5XhqzP

PostgresqlDatabase multithreading performance problem

closed

NONE

Hello, I have a postgresql db connection: ``` database = PostgresqlDatabase(config_server['database_name'], **{'host': config_server['host'], 'port': config_server['port'], 'user': config_server['user'], 'password': config_server['password'] }) ``` and each thread(4 thread) runs the below function with different date_time parameter, we must run the below function 100 times: ``` def get_estimations_v1(date_time, db) -> pd.DataFrame: Estimation._meta.set_table_name('est_' + date_time.strftime("%Y%m%d")) try: db.connect(reuse_if_open=True) query = Estimation.select().where( Estimation.date_time.between(date_time - timedelta(minutes=1), date_time)) estimations = pd.DataFrame(list(query.dicts())) return estimations except Exception as ce: logger.error('load of estimations failed for {}, {}', date_time, str(ce)) return finally: db.close() return ``` but the performance is worse than sequential running. anyone have any ideas?

https://api.github.com/repos/coleifer/peewee/issues/2655/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2654

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2654/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2654/comments

https://api.github.com/repos/coleifer/peewee/issues/2654/events

https://github.com/coleifer/peewee/issues/2654

I_kwDOAA7yGM5XHEM-

PostgresqlDatabase:is_connection_usable returns True, although the database is shut down

closed

NONE

I'm using peewee 3.15.4 with psycopg2-binary to connect to a postgres-database. To test how the system behaves in case that the database is not available, I shut the database down. In the code I call `is_connection_usable` to check if the database is available. It returns `True`, although the database is no longer available. The termination of the connection is logged, so it is recognised by any of the modules involved, but it does not propagate up to the `PostgresqlDatabase`-instance. Any ideas what is going on here? ``` ERROR:root:terminating connection due to administrator command server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. ERROR:root:terminating connection due to administrator command server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. ERROR:root:connection already closed ERROR:root:connection already closed Database status True ```

https://api.github.com/repos/coleifer/peewee/issues/2654/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2653

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2653/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2653/comments

https://api.github.com/repos/coleifer/peewee/issues/2653/events

https://github.com/coleifer/peewee/issues/2653

I_kwDOAA7yGM5XEtBH

When the connection is maintained, the query suddenly takes a lot of time one day

closed

NONE

I use pypy2.7, When I connect to MySQL, Because of the large amount of data, the paging query used took about 3 seconds to complete all queries at the beginning, but after about seven days, it took 80-90 seconds. When the service was restarted, it was restored. I don't know why, does anyone know?

https://api.github.com/repos/coleifer/peewee/issues/2653/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2652

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2652/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2652/comments

https://api.github.com/repos/coleifer/peewee/issues/2652/events

https://github.com/coleifer/peewee/issues/2652

I_kwDOAA7yGM5W7WLV

Does peewee support PostgreSQL `CREATE INDEX CONCURRENTLY`?

closed

CONTRIBUTOR

I didn't see any mention of [this](https://www.postgresql.org/docs/current/sql-createindex.html#:~:text=Normally%20PostgreSQL%20locks%20the%20table,the%20index%20build%20is%20finished.) in code, docs, or past issues (apologies if I didn't search thoroughly enough). My guess is it doesn't, but figured I'd ask just in case. If that's so, would you be open to a PR?

https://api.github.com/repos/coleifer/peewee/issues/2652/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2651

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2651/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2651/comments

https://api.github.com/repos/coleifer/peewee/issues/2651/events

https://github.com/coleifer/peewee/issues/2651

I_kwDOAA7yGM5W5r4G

Allow usage of __init_subclass__ in Models

closed

CONTRIBUTOR

Currently, one cannot use `__init_subclass__()` on `Model`s. This is useful, if one wants to create an abstract model to be implemented with different parameters. Unfortunately `ModelBase` currently hands off all kwargs to the parent type `type` resulting in `TypeError`s: ```python from peewee import Model class MyTemplate(Model): def __init_subclass__(cls, *args, some_param: str, **kwargs): super().__init_subclass__(*args, **kwargs) if some_param is not None: cls.SOME_PARAM = some_param class MyImplementation(MyTemplate, some_param='hello world'): pass ``` Resulting in: ```shell $ python3 test.py Traceback (most recent call last): File "/root/test.py", line 13, in <module> class MyImplementation(MyTemplate, some_param='hello world'): TypeError: __new__() got an unexpected keyword argument 'some_param' ```

https://api.github.com/repos/coleifer/peewee/issues/2651/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2650

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2650/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2650/comments

https://api.github.com/repos/coleifer/peewee/issues/2650/events

https://github.com/coleifer/peewee/issues/2650

I_kwDOAA7yGM5W4uc8

affairs exist concurrency Error

closed

NONE

 `if __name__ == '__main__': t1 = threading.Thread(target=sell2) t2 = threading.Thread(target=sell2) t1.start() t2.start() t1.join() t2.join()` sorry i don't speak english 我开启了两个线程 一个线程在被修改完成后 另一个线程查不到实时数据 只能查到修改之前的数据（操作都在with db.atomic() as txn:） 并且我没有rollback() 不使用 db.atomic()就正常查询到 但是我需要事务 添加了事务即使数据库修改过数据 在db.atomic()里进行查询也不会查到当前的数据 只会查到之前的

https://api.github.com/repos/coleifer/peewee/issues/2650/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2649

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2649/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2649/comments

https://api.github.com/repos/coleifer/peewee/issues/2649/events

https://github.com/coleifer/peewee/issues/2649

I_kwDOAA7yGM5WgbDv

Build a database (SQLite) with peewee WITHOUT setting in the python code the "name" of the table fields

closed

NONE

Hi everyboby Hope my english will be understable I need to read a folder fulled of Excel file and to feed a sqlite data base: Yes EASY In fact I want to make a tool : I feed a txt file with the name of the folder, the cells (eg: A1, B6, ...) and the names of the datas (eg: firstname, lastname, ...) I lunch a Peewee program which reads the txt file and the folder and build the database The difficulty is on the Class(Model): class mytable(Model): dynamic_data[0]=CharField() "# here "first_name" is in dynamic_data[0] class Meta: database = db CharField() refuses to make an objet with a dynamic name coming from my txt file Who has an solution ? Thank you !

https://api.github.com/repos/coleifer/peewee/issues/2649/timeline

completed

https://api.github.com/repos/coleifer/peewee/issues/2648

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2648/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2648/comments

https://api.github.com/repos/coleifer/peewee/issues/2648/events

https://github.com/coleifer/peewee/pull/2648

PR_kwDOAA7yGM5Cvxas

Remove redundant wheel dep from pyproject.toml

closed

NONE

Remove the redundant `wheel` dependency, as it is added by the backend automatically. Listing it explicitly in the documentation was a historical mistake and has been fixed since, see: https://github.com/pypa/setuptools/commit/f7d30a9529378cf69054b5176249e5457aaf640a

https://api.github.com/repos/coleifer/peewee/issues/2648/timeline

https://api.github.com/repos/coleifer/peewee/issues/2647

https://api.github.com/repos/coleifer/peewee

https://api.github.com/repos/coleifer/peewee/issues/2647/labels{/name}

https://api.github.com/repos/coleifer/peewee/issues/2647/comments

https://api.github.com/repos/coleifer/peewee/issues/2647/events

https://github.com/coleifer/peewee/issues/2647

I_kwDOAA7yGM5WD7L1

make the build system pep518 compatible

closed

NONE

Installation of this package is going to break soon. ``` $ pip install peewee Collecting peewee Using cached peewee-3.15.3.tar.gz (858 kB) Preparing metadata (setup.py) ... done Installing collected packages: peewee DEPRECATION: peewee is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559 Running setup.py install for peewee ... done Successfully installed peewee-3.15.3 ``` does the project has planned to upgrade the build system ?

https://api.github.com/repos/coleifer/peewee/issues/2647/timeline

completed