Timeline for search operation for CSV field sqlite
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 17, 2015 at 8:58 | comment | added | satya prakash Panigrahi | Completely agree with you on the "bad design" part :), anyway we have decided to go for a separate table as we are not able to figure out any other better option. | |
| Apr 16, 2015 at 11:41 | comment | added | Marcus Müller | You would still have to change your table since your string field is not an integer field, and then you'd have to change your software to handle that field. What you describe is what I'd call "a fundamentally bad design decision". | |
| Apr 16, 2015 at 10:07 | comment | added | satya prakash Panigrahi | We have considered this option but the current scenario is like, we already have a working code, up and running wherein there's only one SecID for each UserID. Now there's a new requirement as per which a particular User can have multiple SecIDs. Since there's already a set of existing functions for (SecID-UserID) pair, so we are trying to accommodate this new requirement in our existing environment. Adding a new Table would mean having to add new methods to our program. So this doubt :) | |
| Apr 16, 2015 at 8:02 | history | answered | Marcus Müller | CC BY-SA 3.0 |