Leaderboard

I finished up the last (hopefully) pass through my library a week or two ago. I got permission from my employer to post my SQLite library (I need to decide on a license and mention the funding used to create it). and when I went to try to figure out how to make a openg library (which I still haven't done yet) I saw the SQLiteVIEW library in VIPM. Which is similar to mine. But mine has a few advantages. Gives meaningful errors handles strings with /00 in them can store any type of of LabVIEW value (LVOOP classes, variant with attributes), can handle multistatement querys. has a caching system to help manage prepared querys. As for benchmarks I modified your speed example to use my code (using the string based api I added to mine since to the last comparison), and the SQLiteVIEW demo from VIPM. This is on LV2010f2 winxp Yours Insert 255 Dump 107 This no longer available library that I've been using up until my new one (I'm surprised how fast this is, I think it's from having a wrapper dll handling the memory allocations instead of LabVIEW) Insert 158 Dump 45 SQLiteVIEW Insert 153 Dump 43 Mine Insert 67 Dump 73 The differences in speed between mine and SQLiteView I suspect (since I can't open their code) is that I inlined heavily called VI's (the lose on insert), and handle strings with /00 in them (the decrease on dump). If I changed the benchmark to repeatedly called query's that took longer to prepare, I could make yours and the old library appear slower relative to SQLiteVIEW and mine. I attached snippets of the modified code. Anyway I've been debating with myself on posting mine now since it seems kinda of dickish of me to make a free lib when someone recently released one for sale. Also if I wasn't using an academic licensed version of LabVIEW, I might have put mine for sale as well, so I could easily be in their position. The main reason I was posting it was to add back to the community and have something out there to show for possible future employers as an example of what I can do. Being in an academic research lab I don't get payed well and I have no long term employment guaranties, fortunately I love everything else about my job. Anyway my options I can see now. Don't post it. (If I thought SQLiteVIEW was better than mine then I would be leaning to this route more. I do have some other libraries I considering posting but they have a smaller audience). Just post it how I originally intended. (Since I don't have any association with SQLiteVIEW, their actions shouldn't affect me. There's already been two free SQLite libraries anyway). License mine for non commercial use. (Yours is licensed that way if you didn't notice. but that really limits the legal uses of my code. Also I don't have the interest in defending that limitation. So it's practically the same as putting it there with a bsd or lgpl based license like I originally planned on). Contact the makers of SQLiteVIEW, and either Give them a version of my code so theirs can at least reach feature parity with mine. Then wait some period of time before posting mine in the wild. Offer to consult with them on how to improve their version, so I get my name on their version and some amount of money (This feels like blackmail though).

But then you realize that you just have to right click and select TortioseSVN->Revert to solve all your problems

Perhaps you can build yourself a look-up table (not fast access) of all the users on the domain or a specific group. Usernames&CommonNames.vi

I'm not sure what you're listing, but I've allowed a NULL option in doing something similar sounding, so there was an empty string option, thus always creating at least one entry if the directory was empty, two entries if the directory had one item. Tim

What do you mean? You can insert a single column if multiple columns have been defined. the others just get populated with blanks (unless you have defined a field as NOT NULL) Can you elaborate?