there is also the "problem" that a default sequence is created by DAL even if no sequence_name is specified, or sequence_name is set to None.
still I don't know if this was the intended behavior. On 26 Gen, 16:51, kralin <andrea.pierle...@gmail.com> wrote: > here it is: > > http://code.google.com/p/web2py/issues/detail?id=167 > > thank you. > > On 26 Gen, 15:58, Massimo Di Pierro <massimo.dipie...@gmail.com> > wrote: > > > > > > > > > This is a possible bug. Could you please open a googlecode issue? > > Thanks. > > > Massimo > > > On Jan 26, 4:15 am, kralin <andrea.pierle...@gmail.com> wrote: > > > > Hi guys, > > > I've been trying to use legacy postgres databases that uses a custom > > > sequence name. > > > I'm able to read and write a table, by specifying the sequence_name > > > parameter when declaring the Table object > > > > lets say: > > > > table_name = 'table' > > > db.define_table(table_name, > > > Field('%s_id'%table_name,'id'), > > > Field('filed1','string'), > > > Field('field2','string'), > > > migrate=True, > > > sequence_name = '%s_pk_seq'%tablename) > > > > It the table is created before using web2py everything goes smooth, > > > and I can add values and fields to the table. > > > However I the Table do not exist, web2py creates it without setting > > > the given sequence name. > > > Is this the supposed behavior? or am I mistaken? > > > > If this is currently not supported, maybe I can try to implement it. > > > In that case which file should I work on? sql.py or dal.py? > > > Is still not clear to me which one is the currently developed one...
