Comments on informixdb.connect: Filling In The Blanks

Regarding reading sblob object, here is the code e...

2008-01-18T06:56:00.000-08:00

Regarding reading sblob object, here is the code example:

import informixdb
import datetime
def main(argv=None):
if argv is None:
argv = sys.argv

aud = audit()
aud.init_connection()
aud.analiza()
aud.close_connection()
class audit():
def init_connection(self):
print 'init connection'
audit.conn = informixdb.connect('database_name@instance'
,user='a'
,password='a')
audit.cursor = audit.conn.cursor()
return 1
def analiza(self):
print 'analiza'
audit.cursor.execute("""select message from poll_manager
where appid='user_name'
and to_char (time, '%Y%m%d')>='20080112'
and to_char (time, '%Y%m%d')<'20080113'""")
hl7 = audit.cursor.fetchone()[0]
hl7.open()
f_hl7 = hl7.read(10000)
print f_hl7
def connection(self):
print 'close connection'
self.cursor.close()
self.conn.close()
if __name__ == '__main__':
main()

Great article, Carsten. Thanks.

2007-07-24T07:35:00.000-07:00

Great article, Carsten. Thanks.

"Standard" is to be taken with a grain of salt. sq...

2007-07-23T13:30:00.000-07:00

"Standard" is to be taken with a grain of salt. sqlite supports named, as does cx_Oracle, although I heard cx_Oracle doesn't allow the dictionary to be over-specified. If that's true, the locals() trick goes out the window.

The DB-SIG mailing list has recently reached a consensus for making named parameter support mandatory in a future version of the API spec. Until that happens, you should always check with the documentation of the API in question which parameter style(s) it supports.

Hey!The named parameters is probably the best form...

2007-07-23T12:56:00.000-07:00

Hey!
The named parameters is probably the best form since it appears to be a "standard" across multiple databases.

Love that use of locals(). My solution was to pass a dictionary in as one of my parameters and use the values as needed.