Re: [sqlite] Why do I only get one record?

Igor Korot, on Wednesday, February 19, 2020 04:30 PM, wrote... > > Hi, > > On Wed, Feb 19, 2020 at 2:12 PM Jose Isaias Cabrera > wrote: > > > > > > Thanks, Keith. Darn it! GROUP BY and ORDER BY! Got it, it's working > now. Thanks. > > > > > > > sqlite-users on

Re: [sqlite] Why do I only get one record?

Hi, On Wed, Feb 19, 2020 at 2:12 PM Jose Isaias Cabrera wrote: > > > Thanks, Keith. Darn it! GROUP BY and ORDER BY! Got it, it's working now. > Thanks. > > > > From: sqlite-users on behalf > of Keith Medcalf > Sent: Wednesday, February 19, 2020 03:09 PM >

Re: [sqlite] Why do I only get one record?

Thanks, Keith. Darn it! GROUP BY and ORDER BY! Got it, it's working now. Thanks. From: sqlite-users on behalf of Keith Medcalf Sent: Wednesday, February 19, 2020 03:09 PM To: SQLite mailing list Subject: Re: [sqlite] Why do I only get one record? 1)

Re: [sqlite] Why do I only get one record?

1) In the first two query's, why do you have a condition on the LHS table in the LEFT JOIN conditions? 2) In the last query, why do you have a condition on the RHS table of the LEFT JOIN in the WHERE clause? These would seem to indicate that you are using a LEFT JOIN when you really do not

Re: [sqlite] DRH interview on why/how SQLite succeeded

I just finished listening to this. Really cool. Thanks for ALL of your hard work SQLite team. I appreciate it sincerely. On Wed, Feb 19, 2020 at 12:39 PM Simon Slavin wrote: > > > Podcast / transcription of DRH interview: > > " We talked to Richard about

[sqlite] Why do I only get one record?

Greetings! Newbie here again... ;-) Please take a look at this query, sqlite> SELECT ...> a.ProjID, a.Start_date, a.Finish_Date, a.Target_Go_Live_Date, ...> a.BL_Start, a.BL_Finish, sum(b.AnnualDossier) as Dossier, ...> sum(b.Actuals) as ABTActual, sum(b.EAC) as ABTEAC ...> FROM

Re: [sqlite] DRH interview on why/how SQLite succeeded

Don V Nielsen, on Wednesday, February 19, 2020 01:43 PM, wrote... > > DRH sounds so much more human in the podcast than the DRH I have > assembled > in my head from reading this mailing list. :) > He is human like us, just smarter than most of us. :-) josé

Re: [sqlite] DRH interview on why/how SQLite succeeded

DRH sounds so much more human in the podcast than the DRH I have assembled in my head from reading this mailing list. :) On Wed, Feb 19, 2020 at 11:39 AM Simon Slavin wrote: > > > Podcast / transcription of DRH interview: > > " We talked to Richard about the

[sqlite] DRH interview on why/how SQLite succeeded

Podcast / transcription of DRH interview: " We talked to Richard about the history of SQLite, where it came from, why it succeeded as a database, how its development is sustainably funded and also how it’s the most widely deployed database engine in the

Re: [sqlite] Does VACUUM imply REINDEX?

On 19 Feb 2020, at 4:36pm, Olivier Mascia wrote: > having an apparently sane database (pragma integrity_check and pragma > foreign_key_check successful at least), it would make sense to do : REINDEX, > ANALYZE and then VACUUM as part of final preparation step for archive (the DB > would be

Re: [sqlite] Does VACUUM imply REINDEX?

> Le 19 févr. 2020 à 17:26, Simon Slavin a écrit : > > On 19 Feb 2020, at 4:18pm, Richard Hipp wrote: > >> There is no benefit to running >> ANALYZE after running VACUUM if the ANALYZE data (the content of the >> sqlite_stat1 table) is still up-to-date. > > However, if you have a yearly

Re: [sqlite] Does VACUUM imply REINDEX?

On 19 Feb 2020, at 4:18pm, Richard Hipp wrote: > There is no benefit to running > ANALYZE after running VACUUM if the ANALYZE data (the content of the > sqlite_stat1 table) is still up-to-date. However, if you have a yearly maintenance procedure, it might make sense to include ANALYZE in it.

Re: [sqlite] Does VACUUM imply REINDEX?

On 2/19/20, Olivier Mascia wrote: > Hello, > > As part of a rare database "maintenance"... > Does VACUUM, in essence, implies whatever actions REINDEX would do? > Would REINDEX before VACUUM make any more sense? > > And what about ANALYZE? Would it be wise or useless, to run it after VACUUM?

[sqlite] Does VACUUM imply REINDEX?

Hello, As part of a rare database "maintenance"... Does VACUUM, in essence, implies whatever actions REINDEX would do? Would REINDEX before VACUUM make any more sense? And what about ANALYZE? Would it be wise or useless, to run it after VACUUM? So... Would "VACUUM; REINDEX; ANALYZE;" make any