Sripathi Krishnan

@rookie7799 Thanks for stopping by and reporting. I can't reproduce this issue. Can you double check and confirm?

Working Code: ``` from jinjasql import JinjaSql urls = [ ("google", "https://google.com"), ("yahoo", "https://yahoo.com"), ("fb", "https://facebook.com"), ("twitter", "https://twitter.com"), ] template = ''' INSERT INTO links(name, url) VALUES {% for url...

The issue with this is - when do you call the current_offset function? The canonical way to work with rdbtools is ` callback = MyCallback() parser = RdbParser(callback) parser.parse('/var/redis/6379/dump.rdb') `...

I like the idea of the `| identifier` filter, this is a good feature to have. I think the `db_engine` is also a good parameter. We could use `db_engine` to...

Looking at this issue with a fresh pair of eyes, some additional thoughts. 1. I would like to keep JinjaSQL agnostic of the underlying database engine. Making it aware of...

Hi SuperDubbo, this is a valid suggestion, but right now this isn't something we can support.

@oranagra FYI - I'm working on this feature request, should have a pull request in a couple of days

I pushed a fix for this issue with commit 2dee6577a1f83396be5b6fa8192597ef328b11d8 I feel that the old behaviour is incorrect. Making an assumption about the type of bind parameter is not the...

Great feedback, exactly what I was hoping for. Thanks! I will work on this feedback this week. * re. 32 bit version, and keeping it working for older versions -...

Quick update - I've been able to get the memory analysis a lot better. But I haven't got the time to work on the python callbacks. I would like to...