home.social

Search

109 results for “psycopg”

  1. We're heading to Vancouver! 🇨🇦

    Our maintainer Daniele Varrazzo will be speaking at @pgconfdev next week, giving a talk on libpq - the PostgreSQL client library at the heart of Psycopg - and how we can help clients get even more out of PostgreSQL

    If you're attending, don't miss it. And if you're around, come say hello! 👋

  2. We’re happy to share that Daniele Varrazzo, maintainer of psycopg, will be attending @fosdempgday this Friday and @fosdem on the weekend.

    If you’re around, feel free to come say hi and ask him any questions you may have about Psycopg, PostgreSQL or Python database drivers. Drop us a message here if you wish.

    See you soon! 👋

    Photo from PyCon Italia 2022

  3. My next project is the Japanese translation of psycopg3 documentation. 🔌🐘 I expected there's already some past existing work for psycopg2, but couldn't find any, a bit surprisingly.

    Only the home and async pages were finished!

    (Screenshot is locally built from github.com/shuuji3/psycopg/com)

    #psycopg #psycopg3 #translation

  4. Yesterday, on Django 4.2, we bumped #psycopg from v2 to the v3 but suffered an increase in locks & connection waiting during some periods of heavy work on the same hardware (Heroku pg with server-side pgBouncer).

    Operational reasons (shipping!) stop us investigating this in more depth right now but thought this warning may be of help to someone.

    #django

  5. @djangochat @carlton @wsvincent Continuing to talk about Django and PostgreSQL, a Django Chat episode on the recent merge of the Psycopg 3.1+ backend with @felixxm , @apollo13 and @psycopg would be interesting. 🎙️

    As an anticipation we had a great keynote from Daniele Varrazzo at PyCon Italia 2022 @pycon 🇮🇹
    youtu.be/w41jxB37n8M

  6. @djangochat @carlton @wsvincent Continuing to talk about Django and PostgreSQL, a Django Chat episode on the recent merge of the Psycopg 3.1+ backend with @felixxm , @apollo13 and @psycopg would be interesting. 🎙️

    As an anticipation we had a great keynote from Daniele Varrazzo at PyCon Italia 2022 @pycon 🇮🇹
    youtu.be/w41jxB37n8M

    #psycopg #psycopg3 #django #djangochat #python #postgresql #orm

  7. @djangochat @carlton @wsvincent Continuing to talk about Django and PostgreSQL, a Django Chat episode on the recent merge of the Psycopg 3.1+ backend with @felixxm , @apollo13 and @psycopg would be interesting. 🎙️

    As an anticipation we had a great keynote from Daniele Varrazzo at PyCon Italia 2022 @pycon 🇮🇹
    youtu.be/w41jxB37n8M

    #psycopg #psycopg3 #django #djangochat #python #postgresql #orm

  8. @djangochat @carlton @wsvincent Continuing to talk about Django and PostgreSQL, a Django Chat episode on the recent merge of the Psycopg 3.1+ backend with @felixxm , @apollo13 and @psycopg would be interesting. 🎙️

    As an anticipation we had a great keynote from Daniele Varrazzo at PyCon Italia 2022 @pycon 🇮🇹
    youtu.be/w41jxB37n8M

    #psycopg #psycopg3 #django #djangochat #python #postgresql #orm

  9. This morning @felixxm merged the branch for @psycopg 3 support in Django 🎉

    I opened the related issue 13 months ago and since then many developers have worked on the PR based on the work of Daniele Varrazzo 👏

    I thank everyone who made this achievement possible starting from @apollo13 to @felixxm but also Simon Charette, Tim Graham, @adamchainz, @carlton and @davidsmith 🙏

    I'm sure that both Django and Psycopg will benefit from this success ✨

    #django #psycopg3 #psycopg

    code.djangoproject.com/ticket/

  10. Django 4.2 supports Psycopg 3 📢 💥 Thanks to Daniele Varrazzo, @apollo13 and Simon Charette for their humongous work 🌟 🌟 🌟

    github.com/django/django/pull/

    #psycopg3 #postgresql :postgresql: #django :django:

  11. Django 4.2 supports Psycopg 3 📢 💥 Thanks to Daniele Varrazzo, @apollo13 and Simon Charette for their humongous work 🌟 🌟 🌟

    github.com/django/django/pull/

    :postgresql: :django:

  12. Django 4.2 supports Psycopg 3 📢 💥 Thanks to Daniele Varrazzo, @apollo13 and Simon Charette for their humongous work 🌟 🌟 🌟

    github.com/django/django/pull/

    #psycopg3 #postgresql :postgresql: #django :django:

  13. Django 4.2 supports Psycopg 3 📢 💥 Thanks to Daniele Varrazzo, @apollo13 and Simon Charette for their humongous work 🌟 🌟 🌟

    github.com/django/django/pull/

    #psycopg3 #postgresql :postgresql: #django :django:

  14. RT @psycopg

    Psycopg 3.1.5 released. A few bug fixes and *big* speedup improvements: networking, namedtuples, arrays...

    Try it out now! 😄🚀

    github.com/psycopg/psycopg/blo

  15. @Crocmagnon @psycopg has a lot of new features, you can read about them directly in its website 👇
    psycopg.org/

  16. #psycopg est un connecteur #Python à un serveur #PostgreSQL. L'un de nos développeurs, Denis, vous parle plus spécifiquement des #rowFactories => dali.bo/202206_psycopg

  17. Any #python #psycopg people know why this works

    ```
    #results = conn.execute('SELECT (embedding <=> %s) as distance, abstract FROM documents ORDER BY embedding <=> %s LIMIT 5', (query_embedding, query_embedding, )).fetchall()
    ```

    But this throws an error
    ```
    results = conn.execute(f'SELECT (embedding <=> {query_embedding}) as distance, abstract FROM documents ORDER BY embedding <=> {query_embedding} LIMIT 5').fetchall()
    ```

    error in the thread

  18. Django 4.2 supports Psycopg 3 📢 💥 Thanks to Daniele Varrazzo, @apollo13 and Simon Charette for their humongous work 🌟 🌟 🌟

    github.com/django/django/pull/

    #psycopg3 #postgresql :postgresql: #django :django:

  19. The new @psycopg v3 backend for @django 4.2 is quite ready ✨

    It would be very useful if you could test it in your own project to find any errors and measure variations in performance 📈

    You can already find some tests in the PR ⚗️

    github.com/django/django/pull/

  20. A draft merge request adding a psycopg3 backend to #Tryton

    foss.heptapod.net/tryton/tryto

    It showed that we need to add a feature to python-sql to support the pyformat paramstyle of the the DB-API

    peps.python.org/pep-0249/#para

    Switching to psycopg3 would allow to use server side binding and thus give some freedom when processing long list of ids (as it's common with Tryton's ORM).

    #python #psycopg3 #postgresql

  21. A draft merge request adding a psycopg3 backend to #Tryton

    foss.heptapod.net/tryton/tryto

    It showed that we need to add a feature to python-sql to support the pyformat paramstyle of the the DB-API

    peps.python.org/pep-0249/#para

    Switching to psycopg3 would allow to use server side binding and thus give some freedom when processing long list of ids (as it's common with Tryton's ORM).

    #python #psycopg3 #postgresql

  22. A draft merge request adding a psycopg3 backend to #Tryton

    foss.heptapod.net/tryton/tryto

    It showed that we need to add a feature to python-sql to support the pyformat paramstyle of the the DB-API

    peps.python.org/pep-0249/#para

    Switching to psycopg3 would allow to use server side binding and thus give some freedom when processing long list of ids (as it's common with Tryton's ORM).

    #python #psycopg3 #postgresql