Correction... ... *"... so the database hasn't had the TABLE created to support the feature yet."*
On Sat, Sep 14, 2013 at 12:02 PM, Stephen Chrzanowski <[email protected]>wrote: > Thanks for the input. I'll look into it. Looks cleaner than what I've > got now. > > As for the case, I wanted to make absolutely certain that when I update > based on text and not an ID, the most recent form of the text is put into > play. I didn't want to have the software add Motherboard and MotherBoard > as two distinct rows, so I went all out on making sure that everything > SQLite deals with considers case to be not considered. I could have tried > testing the different methods, but I want to get this thing done before the > weekend is out. (Personal note, the sooner I get this stuff organized, the > sooner the auction starts, the sooner I can get that one item that is in > the auction. ;) Yes... Self serving interests, and the code is suffering! > mwahaha) > > The assemblies portion of the code hasn't been implemented, so the > database hasn't been created to support the feature yet. It's in the > works. The table will contain the Assembly ID as a unique constraint, not > auto-numbered and references the ID tag that the company has put on the > devices. > > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
