Mitar

OK. My mistake. It picked my old version of django-lazysignup. OK, so this testproject works. But django-lazysignup tests are still run if I run all tests for my project. And...

I am getting those failures: ``` Creating test database for alias 'default'... .F..E..F.FFFF.FFF..F.FE.....FF....FFF. ====================================================================== ERROR: test_bad_custom_convert_form (lazysignup.tests.LazyTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/mitar/Library/python/modules/lazysignup/tests.py", line 323, in test_bad_custom_convert_form reverse('test_bad_convert'),...

I think there are two questions here: * What is the syntax. Is it standard SQL, SQLite dialect, MySQL dialect, etc.? What are case sensitivity rules? What are escaping rules?...

BTW, do you care about `VIEW` and `QUERY` keywords? Couldn't we map them to some existing SQL commands, like `CREATE VIEW` and `CREATE MATERIALIZED VIEW`? Then probably `sqlparser-rs` could be...

OK, but I think it will be easier to add to `sqlparser-rs` for placeholders inside `CREATE VIEW` statements instead of adding special additional keywords? You are not really passing directly...

So then I am not sure why it could not then work if Noria would use internally `CREATE VIEW` syntax?

OK, we then understand each other. Good. :-) I will see if and when I will have time to contribute PRs to this and other ideas I have brought up....

> push notifications are tricky because they imply full materialization everywhere Hm, I am not sure if I follow here. Why would that be the case. It only implies full...

Thanks for this explanation. I am not sure though why would then full materialization be needed and not just partial materialization for particular values of `z` the user is requesting...

> I think effectively the way to implement it is using cursors. I agree. Given how common such use case (pagination or infinity scroll) is in my experience with live...