Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

LumoSQL

lumosql.org

Post reply on HN
Print view View original

61–70 of 90 posts

Re: LumoSQL

#61

Post by jitl »

OJFord wrote: post #59
rogerbinns wrote: post #46

Earlier quoted context omitted.

The general test suite is not proprietary, and is a standard part of the code. You can run make test. It uses TCL to run the testing, and covers virtually everything. There is a separate TH3 test suite which is proprietary. It generates C code of the tests so you can run the testing in embedded and similar environments, as well as coverage of more obscure test cases. https://sqlite.org/th3.html

Why is that? Surely that leads to conversations with open source contributors like 'this fails the test suite, but I can't show you, please fix it'?

SQLite doesn’t accept contributions

Re: LumoSQL

#62

Post by knowitnone »

alexjurkiewicz wrote: post #41
90s_dev wrote: post #38

Earlier quoted context omitted.

I'm confused, is this just patch and apply patch?

Yes. It's a small DSL to fork a repository and apply a series of textfile transformations (replace file, replace partial file). But if you give this a cool name, it's a New Idea.

did you say "fork"?

Re: LumoSQL

#63

Post by LiamPowell »

OJFord wrote: post #59
rogerbinns wrote: post #46

Earlier quoted context omitted.

The general test suite is not proprietary, and is a standard part of the code. You can run make test. It uses TCL to run the testing, and covers virtually everything. There is a separate TH3 test suite which is proprietary. It generates C code of the tests so you can run the testing in embedded and similar environments, as well as coverage of more obscure test cases. https://sqlite.org/th3.html

Why is that? Surely that leads to conversations with open source contributors like 'this fails the test suite, but I can't show you, please fix it'?

This isn't an issue as SQLite doesn't accept contributions because they don't want to risk someone submitting proprietary code and lying about its origin.

I've never understood why other large open-source projects are just willing to accept contributions from anyone. What's the plan when someone copy-pastes code from some proprietary codebase and the rights holders finds it?

Re: LumoSQL

#64

Post by jitl »

noduerme wrote: post #20
nicoburns wrote: post #16

Earlier quoted context omitted.

"client" doesn't mean web. Mobile apps, desktop apps, etc are all client-side apps that can run regular SQLite. Think of apps Spotify, WhatsApp, AirBnB, Uber, etc. Not to mention mail clients, web browsers, etc. Probably 90% of non-web clients are using SQLite.

I'm not sure about this, I may be exaggerating, but aren't all four apps you mentioned (Spotify, WhatsApp, AirBnB, Uber) built on Electron? So they'd be using SQLite in the Node portion as their storage. That's their "server side", not client side. For that portion (the locally-run mobile backend - the middleware) I guess it would make more sense... so I see what you're saying. [Edit: Of all 4 things - Maybe only Spo…

Spotify used Chrome Embedded Framework (CEF) not Electron, but it’s similar in that it bundles Chrome and uses webviews to draw UI

Re: LumoSQL

#67

Post by Vvector »

LiamPowell wrote: post #63
OJFord wrote: post #59

Earlier quoted context omitted.

Why is that? Surely that leads to conversations with open source contributors like 'this fails the test suite, but I can't show you, please fix it'?

This isn't an issue as SQLite doesn't accept contributions because they don't want to risk someone submitting proprietary code and lying about its origin. I've never understood why other large open-source projects are just willing to accept contributions from anyone. What's the plan when someone copy-pastes code from some proprietary codebase and the rights holders finds it?

The "plan" is to take out the contaminated code and rewrite it.

Re: LumoSQL

#68

Post by LiamPowell »

Vvector wrote: post #67
LiamPowell wrote: post #63

Earlier quoted context omitted.

This isn't an issue as SQLite doesn't accept contributions because they don't want to risk someone submitting proprietary code and lying about its origin. I've never understood why other large open-source projects are just willing to accept contributions from anyone. What's the plan when someone copy-pastes code from some proprietary codebase and the rights holders finds it?

The "plan" is to take out the contaminated code and rewrite it.

If the rights holder is particularly litigious then I could see them suing even if you agreed to take out their code under the argument that you've distributed it and profited from it. I don't know if there's been any cases of this historically but I'd be surprised if there hasn't been.

Re: LumoSQL

#69

Post by dunham »

alexjurkiewicz wrote: post #41
90s_dev wrote: post #38

Earlier quoted context omitted.

I'm confused, is this just patch and apply patch?

Yes. It's a small DSL to fork a repository and apply a series of textfile transformations (replace file, replace partial file). But if you give this a cool name, it's a New Idea.

The TeX source works like this, too. There is the original tex.web and some change files which get applied when converting it to either a TeX document or pascal source. (These days the pascal is further translated to C.)
Post reply on HN