Re: [sqlite] Date time input

> I hope you will experience such joy as well. Well, I don't ;-) The lack of full ALTER TABLE support frustrates me every time, even though I greatly appreciate most other parts of SQLite and the developers' work. But a more complete SQL statement support would be very, very helpful.

Re: [sqlite] Date time input

On 10/10/2019 07:50, J Decker wrote: It's 'ite' as in 'stalagmite' or 'meteorite' as in rock solid... https://changelog.com/podcast/201 " RICHARD HIPP How do I pronounce the name of the product? I say S-Q-L-ite, like a mineral. So probably

Re: [sqlite] Date time input

On Wed, Oct 9, 2019 at 9:05 PM Keith Medcalf wrote: > > On Tuesday, 8 October, 2019 12:40, James K. Lowden < > jklow...@schemamania.org> wrote: > > >OK, but it needs a better name. What better place than here to debate > >that? ;-) > > >What the opposite of "Lite"? > > It's 'ite' as in

Re: [sqlite] Date time input

On Tuesday, 8 October, 2019 12:40, James K. Lowden wrote: >OK, but it needs a better name. What better place than here to debate >that? ;-) >What the opposite of "Lite"? I believe the PC euphemism is Big and Tall. SQLBAT3? -- The fact that there's a Highway to Hell but only a Stairway

Re: [sqlite] Date time input

Tuesday, October 08, 2019, 7:39:40 PM, James K. Lowden wrote: > OK, but it needs a better name. What better place than here to debate > that? ;-) > SQLOfALot (providing you pronounce SQL as ess-queue-ell and not sequel) Graham ___ sqlite-users

Re: [sqlite] Date time input

On 09/10/2019 10:25, Kevin Benson wrote: On Tue, Oct 8, 2019 at 2:40 PM James K. Lowden wrote: On Tue, 8 Oct 2019 09:06:24 -0700 Jens Alfke wrote: I think the idea of a semi-official ?SQLite++? has been floated here before OK, but it needs a better name. -- SQLiteXTD SQLArdArse.

Re: [sqlite] Date time input

On Tue, Oct 8, 2019 at 2:40 PM James K. Lowden wrote: > On Tue, 8 Oct 2019 09:06:24 -0700 > Jens Alfke wrote: > > > I think the idea of a semi-official ?SQLite++? has been floated here > > before > > OK, but it needs a better name. -- > SQLiteXTD -- -- --Ö¿Ö-- K e V

Re: [sqlite] Date time input

I like SQLoaded! Doug > -Original Message- > From: sqlite-users > On Behalf Of Jose Isaias Cabrera > Sent: Tuesday, October 08, 2019 12:15 PM > To: sqlite-users@mailinglists.sqlite.org > Subject: Re: [sqlite] Date time input > > > James K. Lowden, on Tuesda

Re: [sqlite] Date time input

James K. Lowden, on Tuesday, October 8, 2019 02:39 PM, wrote... > > On Tue, 8 Oct 2019 09:06:24 -0700 > Jens Alfke, on > > > I think the idea of a semi-official ?SQLite++? has been floated here > > before > > OK, but it needs a better name. What better place than here to debate > that? ;-)

Re: [sqlite] Date time input

On 8 Oct 2019, at 7:39pm, James K. Lowden wrote: > Simon Slavin wrote: > >> Converting data to and from a convenient storage format is not the >> job of a DBMS. > > While I have no quarrel with your specific point about date strings, > this particular statement is too broad. Arguably, data

Re: [sqlite] Date time input

On Mon, 7 Oct 2019 18:17:14 +0100 Simon Slavin wrote: > Converting data to and from a convenient storage format is not the > job of a DBMS. While I have no quarrel with your specific point about date strings, this particular statement is too broad. Arguably, data conversion is an inherent,

Re: [sqlite] Date time input

On Tue, 8 Oct 2019 09:06:24 -0700 Jens Alfke wrote: > I think the idea of a semi-official ?SQLite++? has been floated here > before OK, but it needs a better name. What better place than here to debate that? ;-) What the opposite of "Lite"? I don't know. It's like asking for the opposite

Re: [sqlite] Date time input

Jens Alfke, on Tuesday, October 8, 2019 12:06 PM, wrote... > > > > On Oct 8, 2019, at 5:34 AM, Jose Isaias Cabrera, on > > > > No, that is not what I was trying to say or ask. Not even close. What I was > trying to say, and most of you missed it was, that if I give date a date > format, > and

Re: [sqlite] Date time input

> On Oct 8, 2019, at 5:34 AM, Jose Isaias Cabrera wrote: > > No, that is not what I was trying to say or ask. Not even close. What I was > trying to say, and most of you missed it was, that if I give date a date > format, and I also provide the format of how that date is to be understood, >

Re: [sqlite] Date time input

Jens Alfke, on Monday, October 7, 2019 09:18 PM, wrote... [clip] > I swear, half the questions on this list build down to "Why doesn't > SQLite act like MS Access?" If you need all the bells and whistles of > formatting > input and output, then use a fancy DBMS application. SQLite is for

Re: [sqlite] Date time input

>Because that's locale-dependent. Some countries, like the US, use >month/day/year; most other countries use day/month/year. Maybe. Canada supposedly uses the day/month/year format, or so I suddenly became aware of in 1998 when I was in my mid 30's. Prior to that day it was m/d/y. Then

Re: [sqlite] Date time input

> On Oct 7, 2019, at 6:17 AM, Jose Isaias Cabrera wrote: > > I have to ask this question: Why is it that the date function does not take > a '4/5/2019' and returns '2019-04-05'? Because that's locale-dependent. Some countries, like the US, use month/day/year; most other countries use

Re: [sqlite] Date time input

On 07 Oct 2019, at 17:19, Keith Medcalf wrote: > On Monday, 7 October, 2019 07:17, Jose Isaias Cabrera > wrote: > >>I have to ask this question: Why is it that the date function does not >>take a '4/5/2019' and returns '2019-04-05'? > > Because it does not. Humans read things in big endian

Re: [sqlite] Date time input

Hi, Jose, Re: Wishing out loud. Maybe an implementation of sscanf() would be more useful generally. As to your date parsing problem, if you really insist on doing it in sql, you may already know how to accomplish it with something like the UPDATE below: .mode column .headers on create table

Re: [sqlite] Date time input

On 7 Oct 2019, at 2:17pm, Jose Isaias Cabrera wrote: > I have to ask this question: Why is it that the date function does not take > a '4/5/2019' and returns '2019-04-05'? Those are human formats. SQLite is a database management system. Its job is to store data and allow it to be recalled

Re: [sqlite] Date time input

On Monday, 7 October, 2019 07:17, Jose Isaias Cabrera wrote: >I have to ask this question: Why is it that the date function does not >take a '4/5/2019' and returns '2019-04-05'? Because it does not. Humans read things in big endian order. For example, in the common base 10 system used

Re: [sqlite] Date time input

. From: sqlite-users [sqlite-users-boun...@mailinglists.sqlite.org] on behalf of Jose Isaias Cabrera [jic...@outlook.com] Sent: Monday, October 07, 2019 9:17 AM To: sqlite-users@mailinglists.sqlite.org Subject: [sqlite] Date time input Greetings. I have to ask this question: Why

[sqlite] Date time input

Greetings. I have to ask this question: Why is it that the date function does not take a '4/5/2019' and returns '2019-04-05'? This may have been asked before, and the answer may be some where in the internet, but, I could not find it. The other thing is that it would be nice to have date