Erlend Egeberg Aasland <erlend.aasl...@innova.no> added the comment:
This is a good idea, but I think the Python interface should stay the same. >From the user perspective, you'd only need to implement the 'value' and >'inverse' callbacks to transform your aggregate class into an aggregate window >class. >From the CPython perspective, we'd only need to use >sqlite3_create_window_function() instead of sqlite3_create_function_v2(), if >we are compiling against SQLite 3.25.3 or newer. I guess it would be nice to output a warning if the user aggregate class contains 'value' and 'inverse' callbacks, but sqlite3 _doesn't_ support aggregate window functions. ---------- nosy: +erlendaasland _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue40617> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
