SQLite

6 ms·

61.
by SQLite 5y ago
I like anamexis's explanation better than my own (that I was typing in concurrently). :-) I'm going to upvote his...
62.
by SQLite 5y ago
No date/time data type will meet everybody's requirements. Some date/time formats will have a limited range, or won't have enough precision, and on the other hand, some date/time type implementations will give lots
63.
by SQLite 5y ago
The ANY datatype in STRICT mode behaves the same as a column with no datatype at all in ordinary SQLite. ANY does not give you any new capabilities.
64.
by SQLite 5y ago
The SQLite dev's internal performance testing using cachegrind shows that STRICT mode uses about 0.34% more CPU cycles. So STRICT is slightly slower, but not enough that you could measure the difference reliably in a real-world syste
65.
by SQLite 5y ago
The incorrect merge is preserved because that is what actually happened. The incorrect merge was published. People saw it (and commented on it in the SQLite Forum). If I "disappear" the merge, that would be airbrushing history.
66.
by SQLite 5y ago
Fossil does not have a "rebase" command, but anything you can do with rebase you can do in Fossil, and more. Fossil allows you (for example) to fix typos in the commit messages of published branches, safely and in a way that does
67.
by SQLite 5y ago
coincidence
68.
by SQLite 5y ago
Scan this HN thread to see comments from devs who are aghast. :-)
69.
by SQLite 5y ago
In something like this: CREATE TABLE t1(a INT, b TEXT); INSERT INTO t1(a,b) VALUES(1,'2'); SELECT * FROM t1 WHERE a=?; The type of the ? is ambiguous. You can say that it "prefers" an integer, but most RDBMSes will also
70.
by SQLite 5y ago
Complete history: https://www.sqlite.org/docsrc/finfo/pages/security.in The title was updated today in response to one of the posts above.
71.
by SQLite 5y ago
We accept (quality) patches and contributions from people who have completed the necessary paperwork to put their patches/contributions in the public domain. This restriction is in place so that that SQLite itself can remain in the pu
72.
by SQLite 5y ago
See https://www.sqlite.org/src/reports?type=ci&view=byuser SQLite has had about 33 contributors (after you combine people using multiple login names). But 92% of the commits have been from just two people. 97% fro
73.
by SQLite 5y ago
> [Fossil is] basically incapable of rewriting your development branch into something more logical... False. All you need to do is start a separate "presentation branch" and cherrypick and/or merge changes from your &quot
74.
by SQLite 5y ago
> would sqlite really be worse today if you hadn't done your own VCS. Yes. Fossil is not only the VCS for SQLite, Fossil is also built around SQLite. SQLite is a core component of Fossil. Thus, when I am working on Fossil, I am f
75.
by SQLite 5y ago
Maybe you could steal ideas and/or code from Fossil to add to Git in order to make Git better?
76.
by SQLite 5y ago
I am the developer of Wapp. I gather (from other comments) that the name "Wapp" collides with a recent pop song by someone named "Cardi B" - please correct me if I have misunderstood. For the record: * I do not fo
77.
by SQLite 5y ago
Linode doesn't follow the cafeteria pricing style. You buy a package. $40/month is the minimum for us to get the disk space and I/O bandwidth we need. We could get by with less CPU, perhaps, but the extra memory and extra
78.
by SQLite 5y ago
Look again. The entire Althttpd website is 100% dynamic. Notice that the hyperlink at the very top of this HN article is to a Markdown file (althttpd.md). A CGI runs to convert this into HTML for your web-browser. The core SQLite website
79.
by SQLite 5y ago
The "z" prefix is intended to denote a "zero-terminated string", or more specifically a pointer to a zero-terminated string.
80.
by SQLite 5y ago
Fossil does has the ability to squash commits. The difference is that Fossil does not promote the use of commit-squashing. While it can be done, it takes a little work and knowledge of the system. Consider the premature-merge problem in w
81.
by SQLite 5y ago
Indeed. And a Citation biz-jet is way faster, flies higher, goes further, and carries more passengers than a Carbon Cub. On the other hand, the Citation costs more, burns more gas, takes more maintenance, and is more complex to fly, and y
82.
by SQLite 5y ago
See https://www.sqlite.org/fts3.html#custom_application_defined_... Since 2016, arguments to the fts3_tokenizer() function must be variables (ex: ? or :var or @var or $var) to which values are supplied by the application at
83.
by SQLite 5y ago
SQLite requires that the self-reference be in the top-level FROM clause of the recursive part of a recursive CTE. PG apparently allows the self-reference to be down inside of subqueries, as long as there is only one reference. I have make
84.
by SQLite 5y ago
The language in the rebase article [1] has been softened somewhat. [1]: https://fossil-scm.org/home/doc/trunk/www/rebaseharm.md
85.
by SQLite 5y ago
I consider a version control system to be a history of a project. If you change the history to something that is materially different, which rebase does, then you are lying about the history. You cannot white-wash this fact. The history G
86.
by SQLite 5y ago
This is misinformation. SQLite does not execute arbitrary code found in the data file. There was a bug, long since fixed, that could be used by an attacker to cause arbitrary code execution upon opening the database file. The reference
87.
by SQLite 5y ago
Newly registered users still don't have access to chat. I think if you add the "C" privilege to the generic "reader" user, that will solve the problem.
88.
by SQLite 5y ago
It's a fair question. I need to better document the security features built into Fossil. Here is a quick off-the-top-of-my-head summary: (1) Fossil is designed to run inside a minimal chroot jail. The stand-alone "fossil" b
89.
by SQLite 5y ago
Thanks for the demo server, exikyut. Maybe: Go to the Setup/Access page and select the "Allow users to register themselves" checkbox, and add permission "C" to "Default privileges". Then press Apply. Wit
90.
by SQLite 6y ago
There was a bug in an older version of SQLite that CheckPoint was able to exploit. That bug has been fixed for a long time. It was fixed even before the referenced talk was given. They had to use an older version of SQLite in that talk so

More ›