Użytkownik Ed Leafe napisał: > > The _newQuery simply allows the framework to skip determining field > types if the columns returned by the new query are identical to the previous > query. So even if the data changes, the column types do not. > >
It's odd because for child bizobj SQL always change when parent change, although columns doesn't. It's because parent link is passed in SQL not as parameter. This is why you may even didn't noticed this issue. > Are you saying that you ran two queries against the same columns, and > got different data types back from the same column on each query? I've never > seen this happen. If the first time a column is queried it returns a certain > data type, I would expect it to always return the same data type. > > Yes, this is exactly what I'm saying. Just create bizobj with float field and requery it, and look into cursor._records dataset each time. > Because those are temporary cursors, and are not guaranteed to return > the same object on subsequent calls. There is no need for (and no way to > guarantee) the sort of optimization that _newQuery affords. > So, optimization should be off by setting _newQuery to True, not False, isn't it? Otherwise regular query return decimal and safe return float instead for the same data. -- Regards Jacek Kałucki _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
