https://bugs.kde.org/show_bug.cgi?id=421126
--- Comment #2 from JAH <vanques...@gmail.com> --- Thanks for the tip re: .kmy files being compressed XML - I didn't know that. Yes I'm sure the field has been populated in my database (even though it has no default value as you point out). To test for yourself: 1. Populate the field with one of the Market codes from the drop down box. This code will persist through successive edits. 2. Populate the field with anything else. It will be saved correctly first time but it will NOT persist through an edit of that field. Since existing market codes DO survive persistent editing, I wondered if this behaviour is by design as a way of validating entries against the drop-down list but that would seem to be unnecessarily proscriptive - precluding the entry of any market codes now or in the future that are not already in the list. Furthermore validation does not explain how ad-hoc entries survive being stored in the first place. It seems that when selecting the TradingMarket field in the Security > Edit dialog, the first entry in the drop-down list is blank and if left unchanged, any existing data is over-written with NULL when the record is saved. I believe more normal behaviour would be for the first item in the drop down list to be populated with any existing data in the record thus ensuring that, without further action, the existing entry/data is preserved. -- You are receiving this mail because: You are watching all bug changes.
