homepage

When I try to use placeholders in CREATE TRIGGER (for django-denorm module) SQLite module just ignores placeholders and sends `None` to it.
For example:
 In [11]: c.cursor().execute('CREATE TRIGGER test1 after insert on a for each row begin UPDATE a SET b=?; END', '1').fetchone()
 In [12]: c.cursor().execute('INSERT INTO a values (100)')
 Out[12]: <pysqlite2.dbapi2.Cursor at 0x101d77e30>
 In [13]: c.cursor().execute('SELECT * FROM a').fetchall()
 Out[13]: [(None,), (None,), (None,)]
 In [14]: c.cursor().execute('DROP TRIGGER test1')
 Out[14]: <pysqlite2.dbapi2.Cursor at 0x101d77f10>
 In [15]: c.cursor().execute('CREATE TRIGGER test1 after insert on a for each row begin UPDATE a SET b=1; END').fetchone()
 In [16]: c.cursor().execute('INSERT INTO a values (100)')
 Out[16]: <pysqlite2.dbapi2.Cursor at 0x101d77f80>
 In [17]: c.cursor().execute('SELECT * FROM a').fetchall()
 Out[17]: [(u'1',), (u'1',), (u'1',), (u'1',)]
In MySQLdb and psycopg2 creating triggers with a placeholder works.

Can we have a reply to this please as I don't understand enough about sqlite3 to comment.

For comparison:
Python 3.1.3:
[(b'',)]
Python 3.2.5:
[(None,)]
Python 3.3.5:
[(b'',)]
Python 3.4.1:
sqlite3.OperationalError: trigger cannot use variables

The sqlite3 module is not at fault here. If it does not work, then is is a restriction of SQLite3 - at which places it accepts bind parameters.
This closing as "not a bug".