I complete ripped up my code.. Working back through an argument to __init__ the object which inherits from my data model.. DUH!
Thanks.. found it. You were create =None killed it.. John On Wednesday, January 16, 2013 10:56:44 PM UTC-6, Michael Bayer wrote: > > > On Jan 16, 2013, at 11:42 PM, jgruber wrote: > > > I'm using SQLAlchemy 7.8 with sqlite3. > > > > I have a Column setup in my schema of type Text, defined as follows: > > > > marker_data = Column(Text(length=None, convert_unicode=False, > assert_unicode=None), nullable=False, unique=True) > > > > I create my object and I see the SQL generated just fine. I have an > external sqlite client looking at the data and I see the table row populate > correctly with the marker_data column when I create objects through > SQLAlchemy and commit them. However, the marker_data attribute on my > python object for the Text fields is set to 'None' as soon as I commit or > read it again from the db. > > > > The text I put in is about 1700 characters and has '\n' characters in > it. Removing the '\n' characters didn't change the behaviour. > > > > When I use the engine by itself and do a raw query with engine.execute() > the tuple data for the Text field comes back just fine. It seems to be the > ORM populating my object's marker_data attribute which isn't working? > > > > Any ideas? How do I troubleshoot this further? > > there's something you're doing that is either setting this field to None > or making it appear that way. would need more details (like a test case) > to see exactly what it is. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To view this discussion on the web visit https://groups.google.com/d/msg/sqlalchemy/-/K6mArBXwxLEJ. 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.
