Closed louking closed 7 years ago
@louking, could you check if this is still a problem with sqlalchemy-datatables>1.0.0?
I have to admit I am a bit afraid to try to update to the latest version, and have just been content with my fork. I have a lot of code which uses sqlalchemy-datatables, and the regression testing to do the update would take some time, I think. Unfortunately I have other priorities I have to be working on at the moment.
On Thu, Feb 9, 2017 at 9:13 AM, Thijs Damsma notifications@github.com wrote:
@louking https://github.com/louking, could you check if this is still a problem with sqlalchemy-datatables>1.0.0?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Pegase745/sqlalchemy-datatables/pull/57#issuecomment-278651918, or mute the thread https://github.com/notifications/unsubscribe-auth/AA1agh0MGZM0qNmCiIgZlBOd2p_X4Yl_ks5rax75gaJpZM4JZEP5 .
Ok, fair enough. I'll closing this PR for now. Hope you have time to see if the current version works for you in the future.