Re: [sqlite] Things you shouldn't assume when you store names

On 11/10/19 1:21 AM, Gary R. Schmidt wrote: So what happens when someone from a family who only uses first- and last-names moves to Kansas? Do they have to make up a middle-name so that he idiots can fill out the forms? I am most definitely not going to take one side or the other. My only

Re: [sqlite] Mailing list shutting down...

May I respectfully suggest to everyone that offering solutions, while valuable and helpful, may not be as valuable as the offer of assistance to our listmaster. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] Advice for a "how-to" situation.

On 2/15/18 2:55 PM, Simon Slavin wrote: By the way, your use of backticks to identify column names That's a quirk of the "schema" command that I used to export the sample that I'm playing with. However, thanks for the reminder. And thanks to everyone for the advice on how to do this. I'm

[sqlite] Advice for a "how-to" situation.

This might be a general RDBMS question but since I'm using sqlite specifically, I hope it passes basic relevancy tests. I have a table defined as: CREATE TABLE "CPUModelDictionary" ( `vendor_id` TEXT, `cpu_family`INTEGER, `cpu_model` INTEGER,

Re: [sqlite] Minor bug reports during build.

On Fri, Dec 22, 2017 at 10:26 AM, Warren Young <war...@etr-usa.com> wrote: > On Dec 22, 2017, at 7:07 AM, Michael Tiernan <michael.tier...@gmail.com> > wrote: > > > > "Working as advertised" Okay, that's just funny. That it doesn't build is > > cor

Re: [sqlite] Minor bug reports during build.

"Working as advertised" Okay, that's just funny. That it doesn't build is correct? Also, despite the "disable-tcl" flag, the tests all fail because of something involving tcl. Don't think I read that in the advertisement. Just as an FYI, it builds correctly on MacOSX and doesn't complain about

Re: [sqlite] Minor bug reports during build.

I found that if I use "disable-tcl" it builds correctly. (Testing is an issue but that's separate right now. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Minor bug reports during build.

war...@etr-usa.com> wrote: On Dec 21, 2017, at 11:37 AM, Michael Tiernan <michael.tier...@gmail.com> wrote: > > I'm trying to build two copes of sqlite3 in a shared dropbox folder. Do you intend to use SQLite inside the Dropbox folder once you’ve got it working? That’s only safe

Re: [sqlite] Minor bug reports during build.

Here's my error report. I'm trying to build two copes of sqlite3 in a shared dropbox folder. It's crude but I'm doing it to prove the ability I want. On a "Scientific Linux 6.7" (RHEL 6.7) system I did a built then build install *as a user* and not as root. Looking to create a localized copy

Re: [sqlite] Minor bug reports during build.

Thank you. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Minor bug reports during build.

Is there a route for reporting an error for an average user without creating an account and all the overhead of the ticket system? ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] SQLite Recursive Common Table Expression suggestion

On Mar 7, 2017 6:56 AM, "Brian Curley" wrote: > I have successfully coupled shell scripts and the CLI I'd love to see examples of this sort of use case and I suspect that there's others who would benefit from seeing how others approach solving some of the common problems.

[sqlite] Documentation clarification request... (re: Triggers)

In the online documentation: https://sqlite.org/lang_createtrigger.html It says: At this time SQLite supports only FOR EACH ROW triggers, not FOR EACH STATEMENT triggers. Hence explicitly specifying FOR EACH ROW is optional. FOR EACH ROW implies that the SQL statements specified in

[sqlite] Foreign key integrity checking.

I'm going to assume this has come up before so instead of asking for help, I'll simply ask for pointers to FAQs about some of the more mundane things such as ensuring foreign key integrity and checking for it. Thanks for everyone's time. -- << MCT >> Michael C Tiernan.