In my day job, I am an SAP consultant - for over 20 years. Production quality code? Yes, but only within the companies where I have worked - tax, banking, inventory, procurement, sales, etc.
My interest in SQLite is a personal hobby project at the moment. I have a couple of ideas for end user applications - a game (tentatively called "Canibal Ants") and a planning tool. Both of them would modeled with graphs (as in graph theory). Given the choice of complex core application code or a complex DB schema, I prefer the latter. At this stage, I am trying to understand the strategies used by experienced SQLite library users to solve common programming problems. I will investigate the shell_callback function. On 17 January 2018 at 19:21, petern <peter.nichvolo...@gmail.com> wrote: > Take a look at the function shell_callback for hints. See the MODE_Csv > case. > You could start by cribbing the functions MODE_Csv uses for your own row > handler and then see what you'll have to figure out yourself. > > Typically, if you are a serious product developer at a frontier in the > market, you will have to fairly expertly code and deploy your own > program(s) for every target platform on which you want your application to > get off the ground. If what you're doing is worthwhile, then you will have > to somehow develop the code to make it happen. That's the development > process. > > Let me ask some questions anybody reading your posts is definitely > wondering about. > > What is your background? Have you done production quality software > development work before? > > Is your application worthwhile? If you can say, what does your application > do for the end user that they couldn't do without it? > > > > > > > > > On Wed, Jan 17, 2018 at 2:54 AM, Shane Dev <devshan...@gmail.com> wrote: > > > On 17 January 2018 at 08:45, petern <peter.nichvolo...@gmail.com> wrote: > > > > > Shane. Expect to do a lot of hacking on shell.c. It's not intended as > a > > > library but as the main program of a console application. > > > > > > That's a shame. I try very hard not to reinvent the wheel especially when > > the wheel question (shell.c) is widely used, flexible and presumably > > thoroughly debugged. > > > > However, I can't be the only one trying to programmatically exchange data > > between SQLite and a delimited text file. For importing, the CSV virtual > > table works well for multi-column CSVs, thanks again for the tip. For > > exporting, I could retrieve the data using sqlite3_exec and build a > string > > from the 3rd and 4th parameters of the callback function. Then I would > need > > to code logic to insert the column and line separators and handle edge > > cases (fields containing separators or double quotes, single column > tables, > > etc) and finally write the string to a file. > > > > Is this most efficient approach? > > _______________________________________________ > > sqlite-users mailing list > > sqlite-users@mailinglists.sqlite.org > > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
