sqlalchemy blows up and puts in addresses instead of data when mixing fields from different dataframes
when composing a class derived from model, populating fields from different dataframes blows up.fields from one data frame are corrupted after session add and session commit fields from another dataframe are fine. building final class object with single dataframe from data frame with the issue alone is just fine. data from the data frame survives session.add and session.commit data is only corrupted when data comes from two different data frame sources field 1 comes from data frame a field 2 comes from dataframe b after session.add session.commit first field from source 1 is corrupted. data from source 2 is fine. again when data source 1 is used by itself with out a second source data from dataframe 1 survives session.add and session.commit. is this a defect in sqlalchemy or in pandas. o -- https://mail.python.org/mailman/listinfo/python-list