This project is archived and is in readonly mode.
Reported by John Woltman | May 1st, 2013 @ 07:49 PM
I have been using psycopg for awhile now, and it's great. I was wondering if support could be added for Postgresql's LTree data type, which can be used to store hierarchies as a field in the database. If the psycopg team does not have time for this feature, I would gladly help implement it if someone can point me in the right direction.
Comments and changes to this ticket
I heavily use ltrees with psycopg (they are just amazing). I use them just as strings. What do you need to implement? They are read-written ok as string, and because the strict rules about the ltree path components you can safely use str.split('.') to tokenize them.
What kind of feature would you implement for an ltree object in python? I suspect an overly specialized object wouldn't add much.
I did not realize that ltrees are treated as strings so easily. My end-goal was to implement an LTree object for Django, and I thought that Psycopg would need to have special support for it as well. But since ltrees can be used as strings, Psycopg support isn't necessary.
From the Django point-of-view, I'll be adding things like childOf, parentOf, etc. methods, but that is a Django thing, and not Pyscopg-specific.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
WARNING: the informations in this tracker are archived. Please submit new tickets or comments to the new tracker.
Psycopg is the most used PostgreSQL adapter for the Python programming language. At the core it fully implements the Python DB API 2.0 specifications. Several extensions allow access to many of the features offered by PostgreSQL.