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

[Michael Tiernan]

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 
suggestion is for anyone to see the depth and complexity of the problem, 
get involved in genealogy. You'll want to scream very quickly. :)


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

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

[Michael Tiernan]

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
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

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

[Michael Tiernan]

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 going to dive in now.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

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

[Michael Tiernan]

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,
`cpuid_level`   INTEGER,
`cpu_model_name`TEXT,
`cpu_cores` INTEGER,
`cpu_MHz`   INTEGER
);
CREATE INDEX `idx_CPUModels` ON `CPUModelDictionary` (
`cpu_family`,
`cpu_model`,
`cpuid_level`,
`cpu_cores`,
`cpu_MHz`
);

that contains rows like this:

'GenuineIntel',6,62,13,'Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz',8,2620
'GenuineIntel',6,63,15,'Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz',8,2600
'GenuineIntel',6,79,20,'Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz',8,1200

The five fields used in the index create a unique identifier.

I want to reference these rows via a single reference field but I'm not 
sure if there's a "smarter" way to do it. I considered just creating a 
field that's a concatenation of the five fields and using that as the 
unique link to the rows but I'm sure that it's not the best way to do it.


(The objective is to have a single field in another table that 
identifies the CPU used in a system. It will be a many-to-one reference 
to this CPUModel.)


Any advice? Pointers to documentation offering advice will help too.

Thanks for everyone's time.
___
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.

[Michael Tiernan]

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
> > correct?
>
> It does build.


Okay, it does build the binaries. Valid point.

  It just doesn’t install to a directory it can’t write to, because you
> told it to install system-level things.



Not going to hash it out here but I didn't tell it to install system-level
things, I told it to compile and install everything locally. Just like I do
with lots of other source packages especially when I'm not very familiar
with the software and wish to make sure of what I'm doing before committing
it to the system.



> > Just as an FYI, it builds correctly on MacOSX and doesn't complain about
> > things it can't control.
> I’m guessing you’re using Homebrew,


Nope, not at all. It doesn't seem to try and touch the things it has no
right to touch.

-- 
<< MCT >>   Michael C Tiernan.http://www.linkedin.com/in/mtiernan

Non Impediti Ratione Cogatationis
Women and cats will do as they please, and
men and dogs should relax and get used to the idea. -Robert A. Heinlein
___
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.

[Michael Tiernan]

"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
things it can't control.
-- 
<< MCT >>   Michael C Tiernan.http://www.linkedin.com/in/mtiernan

Non Impediti Ratione Cogatationis
Women and cats will do as they please, and
men and dogs should relax and get used to the idea. -Robert A. Heinlein


On Dec 21, 2017 10:36 PM, "Rowan Worth"  wrote:

Seems to be working as advertised.
___
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.

[Michael Tiernan]

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.

[Michael Tiernan]

Sorry for the top post. Sadly the android client forces it.

In short, I'm building two copies of sqlite3, one of which works fine, the
attempt to build it on the Linux host (using the prefix flag of course)
causes the build to begin but it to fail when it runs into the attempt at
modifying the (non-existent) file /usr/share/tcl8.5/sqlite3

All the other warnings and considerations are secondary to the point that
the makefile is attempting to change the permissions on an external (to the
user) tool which it neither built or should be able to modify.

Thanks for everyone's time!
-- 
<< MCT >>   Michael C Tiernan.http://www.linkedin.com/in/mtiernan

Non Impediti Ratione Cogatationis
Women and cats will do as they please, and
men and dogs should relax and get used to the idea. -Robert A. Heinlein

On Dec 21, 2017 2:26 PM, "Warren Young" <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 if only one person is using the database at a
time, and you wait for the sync to finish before trying to use the DB on
another machine.

If you need a networked DBMS, SQLite is generally not what you want, at
least not as-stock.  There are add-ons and alternatives that work far
better for this.  Google “SQLite Dropbox”.  It’s come up many times before.

> 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
> specifically.

Try this:

$ ./configure --prefix="$HOME/sqlite3"

That will allow the “make install” to work without root privileges.  The
sqlite3 binary would land in $HOME/sqlite3/bin, with that configuration
option.

You can set the prefix to somewhere under your Dropbox folder if you’re
willing to take the risks to data safety that that entails.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
___
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.

[Michael Tiernan]

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
specifically. At the bottom is the error, the make is attempting to modify
a system tool instead of a local one.

make install
> rm -rf tsrc
> mkdir tsrc
> cp -f /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/alter.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/analyze.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/attach.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/auth.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/backup.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/bitvec.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/btmutex.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/btree.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/btree.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/btreeInt.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/build.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/callback.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/complete.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/ctime.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/date.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/dbpage.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/dbstat.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/delete.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/expr.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/fault.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/fkey.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/func.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/global.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/hash.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/hash.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/hwtime.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/insert.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/legacy.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/loadext.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/main.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/malloc.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mem0.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mem1.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mem2.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mem3.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mem5.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/memjournal.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/msvc.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mutex.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mutex.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mutex_noop.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mutex_unix.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mutex_w32.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/notify.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/os.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/os.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/os_common.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/os_setup.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/os_unix.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/os_win.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/os_win.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/pager.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/pager.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/parse.y
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/pcache.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/pcache.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/pcache1.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/pragma.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/pragma.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/prepare.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/printf.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/random.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/resolve.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/rowset.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/select.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/status.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/shell.c.in
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/sqlite.h.in
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/sqlite3ext.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/sqliteInt.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/sqliteLimit.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/table.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/tclsqlite.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/threads.c
> 

Re: [sqlite] Minor bug reports during build.

[Michael Tiernan]

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.

[Michael Tiernan]

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
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite Recursive Common Table Expression suggestion

[Michael Tiernan]

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.

Does anyone know where knowledge like this is shared? (Specifically aimed
towards users of SQLite?)
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

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

[Michael Tiernan]

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
   the trigger may be executed (depending on the WHEN clause) for each
   database row being inserted, updated or deleted by the statement
   causing the trigger to fire.

So that makes sense (I think) and isn't causing a problem for me but 
then, a little further on it says:


   If a WHEN clause is supplied, the SQL statements specified are only
   executed for rows for which the WHEN clause is true. If no WHEN
   clause is supplied, the SQL statements are executed for all rows.

My quandary comes from the last part of that statement "executed for all 
rows". Does that mean "for all rows in the table" or does it mean "for 
all rows /modified/ in the table" or "all rows previously mentioned as 
being inserted, updated, or deleted by the statement causing the trigger 
to fire"?


I know I can "ass-u-me" what the correct answer should be but I really 
don't have the bandwidth to go and clean up the mess I might make if I'm 
wrong.


Thanks for everyone's time!

--
  << MCT >> Michael C Tiernan. http://www.linkedin.com/in/mtiernan
  Non Impediti Ratione Cogatationis
  Women and cats will do as they please, and men and dogs
   should relax and get used to the idea. -Robert A. Heinlein

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

[sqlite] Foreign key integrity checking.

[Michael Tiernan]

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. http://www.linkedin.com/in/mtiernan
  Non Impediti Ratione Cogatationis
  Women and cats will do as they please, and men and dogs
   should relax and get used to the idea. -Robert A. Heinlein

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