On Apr 1, 2011, at 4:47 PM, rivka wrote: > Hi, > > I have a database where two columns are defined as BigInteger: > > pNum = Column(BigInteger, primary_key=True, autoincrement=False) > pPubDate = Column(BigInteger) > > When I open the database I get two warnings: > /engine/reflection.py:46: SAWarning: Did not recognize type 'BIGINT' > of column 'pPubDate' > ret = fn(self, con, *args, **kw) > > Is that something I should worry about? why am I getting these > messages? Bug or Feature?
It's a feature in that reflection doesn't crash if it receives a column type its not aware exists on the target database, it just ignores trying to create a type object for it and uses "nulltype" instead. It would be a bug if the backend is known to support BIGINT. But you didn't say what backend it is. If its SQLite, SQLite doesn't have types at the column-declaration level anyway, you can use the name "HOTDOG" as a column type and it's happily accepted and will store any value that any other column does, so in the case of SQLite you would stick to that set of type names that SQLAlchemy has decided to recognize for that backend, or just ignore the warning, as BIGINT doesn't need any special processing with sqlite. BIGINT should probably be in the sqlite types list. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
