As I said, I am not a software engineer. I could spend a few hours figuring this out and be fine but it will be painful for me.
I see no downsides in a 64-bit CLI. The last 32-bit Intel CPU was the PIII in 2004, no supported Windows OS requires 32-bit CPUs, the file size may be marginally bigger but who cares on a PC. The 64-bit version will, I assume, happily work on DBs created in the 32-bit version. And for those that need 32-bit for their applications and drivers still have access to the 32-bit DLL. What am I missing? Are windows command line tools 32-bit only? Why add powerful features like CTE if you can't access their power? Isn't this just a matter of making a few changes on some automated scripts that generate each releases files and done? (Sorry if this double posts, I attempted to use Nabble and the message bounced) -----Original Message----- From: sqlite-users [mailto:[email protected]] On Behalf Of Donald Shepherd Sent: Tuesday, August 09, 2016 9:28 PM To: [email protected] Subject: Re: [sqlite] 64-bit SQLite3.exe Why don't you build it yourself as a 64 bit executable? On Wed, 10 Aug 2016 at 00:31 Rousselot, Richard A < [email protected]> wrote: > I would like to request a SQLite official 64-bit SQLite3.exe CLI (not > DLL) be created. > > I have reviewed the prior discussions regarding 64-bit SQLite3 and the > reasoning for which why creating a 64-bit version is denied are "it > does not make a real difference", "you can just use ram disks", etc., etc. > > Here is my plea... I am using a set of complicated CTEs to crawl > through a network (tree) to aggregate and calculate formulas. I don't > have exceptionally large datasets but my CTEs result in a ton of memory usage. > The process works well from disk, in Windows, but using a smaller test > sample I get about a 30% to 40% increase in processing time if I set > the PRAGMA to temp_store = 2. If I use a normal dataset, not a small > test, I hit an approximate 2G limit and get a "out of memory" message, > which I understand is due to SQLite3.exe being 32-bit. I have found > some 3rd party 64-bit builds for SQLite3 (best found is 3.8.5) but > they are out of date and don't allow all functionality that I am > using. So, I do have a use case that requires 64-bit and I would see a > significant increase in speed. > > As to RAM disks, I work in a corporate environment that locks down > user rights which precludes me from distributing a tool that requires > the creation of a tool that needs administrator rights. I also, would > like to avoid having to compile it myself; I am not a software engineer. > > Thanks for your consideration. > > Richard > This communication is the property of CenturyLink and may contain > confidential or privileged information. Unauthorized use of this > communication is strictly prohibited and may be unlawful. If you have > received this communication in error, please immediately notify the > sender by reply e-mail and destroy all copies of the communication and > any attachments. > _______________________________________________ > sqlite-users mailing list > [email protected] > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
