51–60 of 92 posts
SQLlite has also got probably the most well-tested code of conduct of any open source project in the world (aside from the other open source projects which use this CoC) https://sqlite.org/codeofethics.html
I don't think anyone can reasonably get angry over someone else following these. Good rules.
SQLlite has also got probably the most well-tested code of conduct of any open source project in the world (aside from the other open source projects which use this CoC) https://sqlite.org/codeofethics.html
I don't think anyone can reasonably get angry over someone else following these. Good rules.
I'm extremely biased coming from a family with a long tradition of atheism and even anticlerical "militantism".
Earlier quoted context omitted.
Not GP, but PostgreSQL offers jsonb fields[1] Since PostgreSQL allows for functional indexes, you can query and index the data in a structured way. For example you have a table t with "id" and "data" where data is a jsonb field like {foo: ..., bar: ...}. You can do SELECT id, data->'foo' FROM t WHERE data->'bar' > 5 Which will yield the value of "foo" (inside the json field) for rows where "bar" (inside the json fiel…
Unless I'm misunderstanding SQLite can do this as well, but with less nice syntax. The above could be written something like: SELECT id, json_extract(data, '$.foo') FROM t WHERE json_extract(data, '$.bar') > 5 in SQLite. You can also add an index on one of these expressions: https://dgl.cx/2020/06/sqlite-json-support
CREATE INDEX idx_t_bar ON t(json_extract(data, '$.bar'));
CREATE INDEX idx_t_bar ON t(data->'bar');
Also PostgreSQL has many operators[2] which makes using JSON fields easier.
Earlier quoted context omitted.
> No one is required to follow The Rule...[The SQLite developers] view The Rule as their promise to all SQLite users of how the developers are expected to behave. This is a one-way promise, or covenant. In other words, the developers are saying: "We will treat you this way regardless of how you treat us." I don't see a problem here, despite my own disinterest in following the Christian faith or any other. It's not ha…
In fact, that would go against their code of ethics.
Then again, I suppose an argument from behavior may also be less likely to convince an interlocutor more inclined to concern with what someone else believes than with how they actually behave. So it goes.
One of the examples of wildly successful "one-man-army" software (conceived of and built by a single person). See also: Redis, Linux, Doom/Quake, Steve Wozniak, jQuery, Python and countless obscure modern SaaS products.
That has helped ensure there are no forks given quality would be inferior.
It also kept SQLite out of the browser since there are no competing implementations of it.
Don’t forget to count all the cruise missiles, too!
Those tend to fall out of the “active use” category not long after entering it, so it’s probably not a big factor. On a more serious note, had there been something special about SQLite supporting military use of their project that prompted this? Otherwise that’s the point of free software, people are free to do (mostly) whatever they want with it. Including building weapons. SQLite is so prevalent, it’s almost like p…
Earlier quoted context omitted.
Hundreds of SQLite files? In active use? Unless iOS itself spawns a few hundred instances and actively uses them all the time I have a hard time thinking of what would use so many databases, much less that they’re actually in active use.
What does active use really mean? The databases themselves are only accessed for a few nanoseconds at a time.
Earlier quoted context omitted.
Unless I'm misunderstanding SQLite can do this as well, but with less nice syntax. The above could be written something like: SELECT id, json_extract(data, '$.foo') FROM t WHERE json_extract(data, '$.bar') > 5 in SQLite. You can also add an index on one of these expressions: https://dgl.cx/2020/06/sqlite-json-support
That is true, but SQLite doesn't support functional indexing. This means that you cannot do CREATE INDEX idx_t_bar ON t(json_extract(data, '$.bar')); for fast lookups. But you can do CREATE INDEX idx_t_bar ON t(data->'bar'); in PostgreSQL. You have some workarounds like I explained.[1] Also PostgreSQL has many operators[2] which makes using JSON fields easier. [1] https://news.ycombinator.com/item?id=29461926 [2] htt…
SQLite has "Indexes On Expressions"[1] since 2015. I'm assuming functional indexing in Postgres is the same. So I think the syntax would be:
CREATE INDEX idx_t_bar ON json_extract(data, '$.bar');
> Also PostgreSQL has many operators[2] which makes using JSON fields easier.
This does look a little more convenient to write than SQLite's JSON syntax, but I don't see any fundamental difference here.
Earlier quoted context omitted.
I don't think anyone can reasonably get angry over someone else following these. Good rules.
Haha I’d love to agree but it seems there are plenty of people in this thread that are upset about it nonetheless