You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #1637, the idea of being able to define your own nodes using decorators came up.
For example (and I'm speculating here),
@postgres.udf([dt.double, dt.double], dt.double)defmy_node(x, y, **kwargs):
return# things in the "space" of the backend, in this case, it would be SQLAlchemy code
We should think through what this would look like and discuss any relevant details.
The text was updated successfully, but these errors were encountered:
I independently started work on this type of functionality. I didn't follow that API pattern, but I like the decorator style you showed, @cpcloud. If you or anyone else gets a chance, please take a look at my feature branch below and let me know what you think.
One thing that is lacking in the CI suite to make Postgres UDF testing feasible is that the current Postgres image being used doesn't have PL/Python installed. It's using an image that is a much slimmed-down version of Postgres. The easiest fix is to use the standard full version of Postgres. I'm working on creating a new Dockerfile that achieves that, but I haven't got it working yet and haven't pushed any code on that yet.
In #1637, the idea of being able to define your own nodes using decorators came up.
For example (and I'm speculating here),
We should think through what this would look like and discuss any relevant details.
The text was updated successfully, but these errors were encountered: