Hi everyone,
I am William. I am an Electronics Engineering Student, currently working as a Python Programming Intern, and I am working on heavily data-driven backend applications. I am highly interested in contributing to the Add support for generate_series in postgres project under GSoC 2026.
After going through some of the previous forum discussions (@charettes’ insights on virtual tables), I believe the task is not just about patching the generate_series function. It is actually about the architecture because the problem lies with the fact that the ORM does not support the appropriate primitives for set-returning functions and LATERAL JOINs.
In my recent backend-related activities, like creating a stock portfolio tracker and dealing with simulations of financial data, I have witnessed the importance of time series data generation and gap filling firsthand.
I would really love to contribute to the project under GSoC 2026 and work on the above-mentioned problem so that the ORM supports expressions with a return value. I have different ideas to contribute concerning this that definitely be helpful
Before I work on the GSoC application, I would like to get the mentors’ opinions on a few things:
Should the 350 hours be focused on getting the generate_series function working correctly, or should the work heavily focus on creating a generic relation expression so that we can support other SRFs in the future?
Are there any specific open tickets related to ORM aliases that I should probably focus on right away as a ‘good first issue’ to you know, get a feel for the compiler logic?
Looking forward to receiving the feedback and contributing to ORM!
Best regards,
William