> On Mar 24, 2020, at 09:13, Luuk wrote:
>
> No, i do NOT mean the source of the forum, but the source for "The list is
> deprecated"
http://sqlite.1065341.n5.nabble.com/New-SQLite-Forum-established-this-mailing-list-is-deprecated-td111358.html
But that's just DRH. The mailing list is
> On Mar 14, 2020, at 03:14, Justin Ng wrote:
>
> This works fine,
>
> SELECT
>x.sql
> FROM
>temp.sqlite_master AS x;
>
As is this:
SELECT
sql
FROM
temp.sqlite_master;
Hmm.
___
sqlite-users mailing list
> On Mar 13, 2020, at 23:09, Michael Falconer
> wrote:
>
> So I'll take the opportunity now to thank (too many to single out) the many
> contributors to this list who have made it unique, and well...just a nice
> place to be.
So long, and thanks for all the fish :)
Will miss this place.
> On Mar 13, 2020, at 01:04, Keith Medcalf wrote:
>
> Uck. That is the most horrible looking thing I have ever seen in my life.
> Good luck with it.
If only this was confine to the esthetics. But yes, horrible sums it up.
___
sqlite-users
> On Mar 13, 2020, at 00:54, BohwaZ wrote:
>
> So that people wishing to use emails could still do it by subscribing
> to alerts and then replying to notifications.
Also, would it be possible to actually mark such emails to include proper List
Header Fields, e.g.:
List-Id: List Header
> On Mar 12, 2020, at 21:17, Richard Hipp wrote:
>
> a replacement for this mailing list:
Tragic. Oh well. Anyhow, thanks for SQLite itself :)
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
> On Jan 13, 2020, at 19:37, Jens Alfke wrote:
>
>> What is the motivation behind this advice? It's completely unnecessary.
>
> Thanks for your opinion, James! I disagree.
Arnt Gulbrandsen, of Archiveopteryx fame, would disagree with you, Jens :)
https://archiveopteryx.org/schema
In
> On May 7, 2019, at 05:35, Jens Alfke wrote:
>
> [https://en.wikipedia.org/wiki/French_Republican_calendar]
Along the same lines: International Fixed Calendar
https://en.m.wikipedia.org/wiki/International_Fixed_Calendar
> You Advocate An Approach To Calendar Reform; Your Idea Will Not
> On May 6, 2019, at 19:58, Jose Isaias Cabrera wrote:
>
> something is wrong where one week only has 1 day
... per month :P
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
> On May 4, 2019, at 21:24, Thomas Kurz wrote:
>
>> What about just sticking with the ISO week definition?
>>
>> https://en.wikipedia.org/wiki/ISO_week_date
>
> From the document you cited:
>
> "The ISO standard does not define any association of weeks to months."
True enough, even though
> On May 4, 2019, at 15:59, Luuk wrote:
>
> This is the 'standard' used here where i live, so i can accept that ;)
"The nice thing about standards is that you have so many to choose from."
-- Andrew Stuart "Andy" Tanenbaum
:P
___
sqlite-users
> On May 4, 2019, at 12:47, Luuk wrote:
>
> As others have noted, it's a question of definition, and which definition do
> you follow?
What about just sticking with the ISO week definition?
https://en.wikipedia.org/wiki/ISO_week_date
___
> On Nov 27, 2018, at 06:16, Wout Mertens wrote:
>
> If it's on a mac, this terrible misfeature can be turned off in system
> preferences - keyboard - text - smart quotes.
Oh my... right you are :|
Grrr indeed.
___
sqlite-users mailing list
> On Nov 26, 2018, at 21:16, Shawn Wagner wrote:
>
> It's waiting on a plain single quote to end the string. You have a Unicode
> smart quote character U+2019 (’) instead of a ' at the end before the
> semicolon, which doesn't count.
D’oh. Facepalm. Right you are. Long live Unicode! :)
> On Nov 26, 2018, at 20:25, Richard Hipp wrote:
>
> Unable to repro:
Hmmm… ok… then… local problem of some type…
$ uname -a
Darwin 18.2.0 Darwin Kernel Version 18.2.0: Fri Oct 5 19:41:49 PDT 2018;
root:xnu-4903.221.2~2/RELEASE_X86_64 x86_64
$ brew info sqlite3
sqlite: stable 3.25.3
> On Nov 26, 2018, at 20:11, Richard Hipp wrote:
>
> though there probably is not time to get warnings in to the forthcoming
> 3.26.0 release.
Talking of which, the CLI doesn’t seem to handle the following statement very
gracefully:
sqlite> select DATE '1998-12-25’;
...>
...>
…>
> On Nov 20, 2018, at 21:49, Thomas Kurz wrote:
>
>> (Does SQL itself have a numeric timestamp type, or explicitly endorse the
>> POSIX epoch for numeric timestamps?)
>
> SQL has an explicit TIMESTAMP type since SQL-92, one thing that I'm heavily
> missing in SQlite ;-)
DATE '1998-12-25’ &
> On Oct 28, 2018, at 11:32 PM, Keith Medcalf wrote:
>
> will last 50 years (which is 10 times the warranty period)
Thank you.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
> On Oct 26, 2018, at 3:21 PM, Thomas Kurz wrote:
>
>> What'da ya think?
>
> That's a great idea. I've already had some concerns that SQLite development
> might cease now. Hoping for great new features in the next release :-)
MERGE! :D
___
> On Oct 26, 2018, at 5:12 AM, Philip Warner wrote:
>
> knowingly and deliberately ignoring large chunks, and broadly disagreeing
> with even more, and laughing at the rest.
Bah… Everything Is Amazing And Nobody Is Happy:
https://www.youtube.com/watch?v=nUBtKNzoKZ4
> On Oct 25, 2018, at 1:20 PM, Mike King wrote:
>
> I’m more a Mr Creosote kind of guy. Wafer thin mint anybody? :)
Please bring your own bucket. This is SQL*lite*. :P
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
> On Oct 25, 2018, at 12:59 PM, Mike King wrote:
>
> The beer is bloody good and very strong.
"Beer is proof that God loves us and wants us to be happy."
— Benjamin Franklin, allegedly
https://quoteinvestigator.com/2016/06/24/beer-wine/
> Also, I’m happy to report I didn’t go up in flames
> On Oct 25, 2018, at 8:33 AM, Philip Warner wrote:
>
>> The second exhortation tells us that that's not enough, and we also have a
>> duty to maximise pleasure.
>
> lol, good point. Quite the opposite of monkish orders.
And yet…
https://en.wikipedia.org/wiki/Trappist_beer
Let SQLite be
> On Oct 22, 2018, at 11:31 PM, Simon Slavin wrote:
>
> And now has reached the summit of Slashdot's front page:
Slow news day. Good night, and good luck.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
> On Oct 22, 2018, at 11:35 PM, am...@juno.com wrote:
>
> October 22, 2018 Hello Good People: I need to import a large bunch of names
> (first and last), and id numbers into SQ Lite. How do I do en-mas--as opposed
> to copying and pasting each individual name, clock number, etc? I would be
>
> On Oct 22, 2018, at 10:32 PM, Donald Shepherd
> wrote:
>
> It's disappointing
Why so serious? Plus, really, what have the romans ever done for us?
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
> On Oct 22, 2018, at 9:43 PM, Rob Dixon wrote:
>
> weird and antagonistic
Thank you for the kind words of support. Your wisdom and insights will be
missed. Farewell Rob Dixon. Godspeed.
___
sqlite-users mailing list
> On Oct 22, 2018, at 5:29 PM, Richard Hipp wrote:
>
> In summary
Leave it as it is, no one is going to loose sleep over it. Now, about that
MERGE command... :)
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
> On Oct 19, 2018, at 11:05 PM, Wout Mertens wrote:
>
> I can live with that.
Yes, let’s get along for once.
In the memorable words of President Dale:
"Why can't we work out our differences? Why can't we work things out? Little
forum people, why can't we all just get along?”
Mars Attacks!
> On Oct 15, 2018, at 5:36 AM, Rowan Worth wrote:
>
> Anyway my point is I'm not seeing evidence to support the assertion that
> gmail treats messages to the list in general as spammish.
Ditto.
___
sqlite-users mailing list
> On Oct 11, 2018, at 6:35 PM, Shawn Wagner wrote:
>
> I'm about ready to unsubscribe from this list and not come back until it
> transitions to a forum (which is the interface I prefer anyways) because of
> all this nattering clogging up my inbox the last few days. I thought I was
> a grumpy
> On Oct 9, 2018, at 7:19 PM, Warren Young wrote:
>
> The arguments about mailing lists vs forums have all been had.
It’s not clear why this entire conversation is presented in such stark terms:
LIST *OR* FORUM. Puzzling.
If this is all driven by DRH edict that “all things shall run on
> On Oct 11, 2018, at 4:51 PM, Balaji Ramanathan
> wrote:
>
> The 1990's called and they want their mailing lists back.
It is/was there all the time. No one moved the cheese yet.
(11) Every old idea will be proposed again with a different name and a
different presentation, regardless of
> On Oct 10, 2018, at 8:31 PM, Warren Young wrote:
>
> addresses can be *forged*
forged fɔːdʒd/ adjective • copied fraudulently; fake.
O no! :(
Perhaps the time has come for you to learn the gory details of that so-called
'Simple Mail Transfer Protocol'! :)
Simple, but
> On Oct 10, 2018, at 8:31 PM, Warren Young wrote:
>
> The next version of Fossil is likely to include a fully-capable SMTP server
Zawinski's Law at work! :D
“Every program attempts to expand until it can read mail. Those programs which
cannot so expand are replaced by ones which can.”
> On Oct 10, 2018, at 6:02 PM, Warren Young wrote:
>
> I’ve written up a long list of advantages to the Fossil forum feature here:
Quixotic, but your dedication has to be applauded.
Could we agree to disagree though?
Or is it a case of "somebody is wrong on the internet”?
> On Oct 9, 2018, at 11:42 PM, Simon Slavin wrote:
>
> On 9 Oct 2018, at 10:38pm, Keith Medcalf wrote:
>
>> And just what is NSFW spam?
>
> Messages purporting to come from young women. Some including images
> purporting to be them in various states of undress.
( How does one subscribe?
> On Sep 11, 2018, at 8:07 PM, Richard Hipp wrote:
>
> We are in final testing for SQLite 3.25.0. Details on this release
> can be seen at
>
> https://www.sqlite.org/draft/releaselog/3_25_0.html
Window Functions! Hurray! Hurray! :)
https://www.sqlite.org/draft/windowfunctions.html
> On Aug 15, 2018, at 11:55 AM, R Smith wrote:
>
> This has been existing for quite a while in SQLite, and not only this, but
> quite a few schema enumeration functions via the table-valued-function form
> of the pragmas.
FWIW, information_schema would be the relevant ANSI-standard in that
> On Aug 14, 2018, at 12:57 PM, Richard Hipp wrote:
>
> I will strive to bring the behavior of SQLite into alignment with PostgreSQL.
If only all this energy was spent on a proper MERGE clause instead… sigh… :D
___
sqlite-users mailing list
> On Apr 19, 2018, at 1:06 PM, Richard Hipp wrote:
>
> We are open to adding MERGE INTO at some point in the future.
Excellent!
> But the UPSERT syntax is both easier to understand
Debatable.
> and easier to implement,
Possibly.
> and we prefer to follow PostgreSQL
> On Apr 19, 2018, at 12:29 PM, Richard Hipp wrote:
>
> The latest pre-release snapshot [1]
Link missing?
> contains support for UPSERT
> following the PostgreSQL syntax.
> The documentation is still pending.
> Nevertheless, early feedback is welcomed. You can respond
> On Nov 21, 2017, at 6:23 PM, Warren Young wrote:
>
> This is what drh does. We’re fans because he does it well.
drh + djb = bliss?
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
> On Nov 21, 2017, at 3:30 PM, Richard Hipp wrote:
>
> I think what we are seeing is the beginning of the end of email as a viable
> communication medium.
Nonsense. Email is one of these cockroach technologies: it will survive us all.
> I really need to come up with an
> On Nov 21, 2017, at 8:42 PM, Warren Young wrote:
>
> As far as I can tell, the only really hard part is the email gatewaying
> problem, evidenced by the fact that Fossil still doesn’t have a feature to
> echo commits, ticket changes, etc. via email.
“Every program
> On Aug 16, 2017, at 11:11 AM, Jean-Luc Hainaut
> wrote:
>
> The implementation of SQLite "group_concat" (a very powerful but often
> overlooked function) provides some but not all the features found in other
> DBMS (MySQL "group_concat" and PostgreSQL
> On Jun 28, 2017, at 4:15 PM, R Smith wrote:
>
> I did ponder whether it would be a nice "feature" to use the default if both
> a DEFAULT and a NOT NULL constraint existed on a column - but then again,
> that will go against strict design principles and can cause a lot of
> On Feb 17, 2017, at 12:21 AM, Warren Young wrote:
>
> How can we expect people to write threaded programs when even a simple
> integer increment is prone to race conditions and read-modify-write errors?
"… we did not (and still do not) believe in the standard
> On Feb 15, 2017, at 11:16 AM, Clemens Ladisch wrote:
>
> SQLite does not have windowing functions.
A continuous/continual tragedy indeed :|
Still, worthwhile mentioning The Tabibitosan Method, for reference purpose:
http://www.orchestrapit.co.uk/?p=53
> On Oct 20, 2016, at 1:58 AM, Bart Smissaert wrote:
>
> I worked it round to get 3 consecutive drops:
>
> but I must have done something wrong as it picked 62 up from this:
It has three consecutive drops, no? E.g. 47 < 46 < 37
Example:
with
DataSet
as
(
select
> On Oct 20, 2016, at 12:23 AM, Bart Smissaert wrote:
>
> Ah, yes, sorry, I needed actually drops and was looking at that.
Just for fun, here is one using recursion:
with
DataSet
as
(
select 1 as id, 2 as key, '2004-06-23' as date, 42 as value union all
select 2
> On Oct 19, 2016, at 11:40 PM, Bart Smissaert wrote:
>
> ID 2 for example shouldn't be selected.
Hmmm? ID 2 has two ‘raises' as per your definition: 39 > 42 > 43 and 42 > 43 >
45
2 2004-06-23 42
2 2006-12-28 39
2 2007-10-09 42
2 2007-10-24 43
2 2009-06-17 45
2
> On Oct 5, 2016, at 11:50 AM, Paul Sanderson
> wrote:
>
> How do I search for a % symbol within a string when % is a wild card
> and I am escaping that very wildcard?
For example:
with
DataSet
as
(
select 'I got 20 quid' as value union all
select 'i got 20%
> On Oct 5, 2016, at 11:38 AM, Paul Sanderson
> wrote:
>
> How casn I find just the rows containing the percent symbol? is it possible?
Use the ESCAPE clause:
"If the optional ESCAPE clause is present, then the expression following the
ESCAPE keyword must
> On Oct 3, 2016, at 11:18 AM, Luca Ferrari wrote:
>
> What is the right way to do it without having to stop the application
> (and therefore without knowing when a new I/O operation will be
> issued)?
You could use the attach/detach [1] functionality to transparently
> On Sep 22, 2016, at 9:04 PM, Richard Hipp wrote:
>
> (https://www.sqlite.org/draft/releaselog/3_15_0.html).
Oh! Row Values! Nice! :)
https://www.sqlite.org/draft/rowvalue.html
___
sqlite-users mailing list
> On Apr 4, 2016, at 6:14 PM, Richard Hipp wrote:
>
> On 4/4/16, Domingo Alvarez Duarte wrote:
>> sqlite knows which table/field failed
>
> No it doesn't, actually.
And yet, that same question comes over, and over, and over, ad nauseam. Each
and every time a poor soul is confronted with
> On Mar 6, 2016, at 9:37 PM, James K. Lowden
> wrote:
>
> I've never seen a system that provides queryable optimizer metadata.
Oracle does, for a given definition of ? queryable?.
> I don't remember ever having read a paper on the idea, either.
I have to confess using query plans to get
> On Dec 21, 2015, at 5:43 PM, Darren Duncan wrote:
>
> Comic act? Do you consider the MERGE defined in the SQL standard to be a
> better designed feature than Postgres' alternative,
Yes.
> or do you prefer the former soley because it is in the SQL standard?
Yes.
> I recall that Postgres
> On Dec 21, 2015, at 4:08 AM, Darren Duncan wrote:
>
> If you want that feature, instead do it the better way that Postgres 9.5 did,
> which is as an extension to the INSERT statement in the form "ON CONFLICT DO
> UPDATE/IGNORE?.
Please, enough of the comic act :P
MERGE it is.
Oh, yes,
> On Dec 20, 2015, at 7:12 PM, Big Stone wrote:
>
> To prepare for 2016 greetings moment, here is my personnal whish list
> for sqlite:
MERGE statement! Yeah! :)
https://en.wikipedia.org/wiki/Merge_(SQL)
> On Sep 13, 2015, at 3:53 PM, E.Pasma wrote:
>
> I just learned that the strftime function returns '0' for Sundays, not 0, and
> that 0<>'0?.
Yes, always compare likes to likes:
with
DataSet
as
(
select strftime( '%w', date() ) as value
)
select value,
typeof( value ) as typeof1,
> On Sep 11, 2015, at 6:31 PM, Richard Hipp wrote:
>
> a passing fad
On the other hand, we can now embrace NormalFormZero without undue
embarrassment. Swell.
> On Sep 11, 2015, at 5:58 PM, Richard Hipp wrote:
>
> JSON support in SQLite
JSON, eh? No MERGE. No analytics. But serialization of the week is covered.
Sweet :D
Perhaps of interest:
http://sqlite-libs.cis.ksu.edu
> Begin forwarded message:
>
> From: St?phane Faroult
> Subject: OT: Oracle functions for SQlite
> Date: September 8, 2015 at 2:30:24 AM GMT+2
> To: "Oracle-L (E-mail)"
> Reply-To: sfaroult at roughsea.com
>
> I don't know if there are
> On Aug 29, 2015, at 11:28 PM, Simon Slavin wrote:
>
> Someone else wrote some code which performed various queries and created
> real TABLEs with the appropriate data in.
Yes, something along these lines:
[[
attach database 'information_schema.db' as information_schema
]],
[[
> On Aug 25, 2015, at 8:53 PM, R.Smith wrote:
>
> I vote to change it every release... Stimulate better habits!
Seconded. Keep them on their toes!
> On Aug 17, 2015, at 12:01 PM, Clemens Ladisch wrote:
>
> Just because the ORDER BY clause refers to a column of the
> SELECT clause does not mean that the value is not computed
> a second time.
And yet:
with
DataSet( position, value )
as
(
select 1 as position,
random() as
> On Aug 17, 2015, at 8:08 PM, R.Smith wrote:
>
> CORRECTION: It seems one of the two options I've mentioned earlier, namely
> the CREATE TABLE AS SELECT... does not actually work on the back of a WITH
> clause. The other option still do, but this request has more appeal now.
Hmmm?!?
create
> On Aug 17, 2015, at 5:44 PM, John McKown
> wrote:
>
> One thing that would be really useful for me in SQLite3 which is in
> PostgreSQL is the INTO phrase.
CTAS? AKA 'create table as'?
> On Jul 22, 2015, at 12:40 AM, R.Smith wrote:
>
> Reminds me of the old saying: I'd rather have a bottle in front of me than a
> frontal lobotomy!
Cheers to that! :D
> On Jun 18, 2015, at 11:11 PM, James K. Lowden
> wrote:
>
> There's a reason Larry Ellison can affort a yacht almost 500 feet long.
And an island to moor it.
In any case, best luck to David and his project. He will need it.
> On Jun 18, 2015, at 5:10 PM, Marc L. Allen
> wrote:
>
> Frankly, I've avoided taking a close look at Andl because of its massive use
> of special characters. I can usually work out a rough meaning on your
> examples because I know the SQL it came from. If I became 'Andl proficient'
> it
> On Jun 14, 2015, at 4:01 PM, david at andl.org wrote:
>
> First, I added a RECURSE() function to Andl, similar to the CTE in SQLite.
Nice.
> The Mandelbrot algorithm looks like this.
Could we see something more, hmmm, pedestrian? Perhaps a simple recursive
query, showing, say, all the
> On Jun 9, 2015, at 2:53 PM, Jean-Christophe Deschamps
> wrote:
>
> Most probably! I can imagine that you don't encounter such style in common
> business-like environments.
Just for ?corporate' fun: analytic recursive common table expression - oh, my?
with
Clock( start_at, end_at,
> On May 20, 2015, at 8:05 PM, Simon Slavin wrote:
>
> "Today, I?ll talk about why we stopped using serial integers for our primary
> keys, and why we?re now extensively using Universally Unique IDs (or UUIDs)
> almost everywhere.?
Argh? seriously?
tl;dr: don?t.
> On Apr 14, 2015, at 11:40 AM, Jonathan Moules
> wrote:
>
> Options that have come to mind (probably missed a lot):
I personally use temp tables, e.g. 'create temporary table if not exists foo?,
coupled with 'pragma temp_store = memory?, and drop/create them as necessary,
e.g. 'drop table
> On Apr 7, 2015, at 5:53 PM, John McKown
> wrote:
>
> I'm an idiot, thanks for not pointing that out. I thought I was on the
> PostgreSQL forum and managed to mess up. My apologies to all.
We all have been there.
I, for one, wish SQLite had some syntax sugar such as PIVOT/UNPIVOT:
> On Mar 18, 2015, at 10:24 PM, Jason Vas Dias
> wrote:
>
> This seems very buggy to me.
Correct.
http://www.styleite.com/wp-content/uploads/2014/11/legallyblonde.gif
> On Mar 18, 2015, at 9:51 PM, Jason Vas Dias
> wrote:
>
> I don't see how anything like that is possible in the sqlite3 shell .
Not in the shell per se, no (.bail on|off may or may not help in your case).
Perhaps ON CONFLICT clause might help you:
https://www.sqlite.org/lang_conflict.html
> On Mar 18, 2015, at 9:45 PM, Jason Vas Dias
> wrote:
>
> Would you care to expand on that ?
As it says on the tin [1]: you cannot start a transactions inside another
transaction (use savepoint if you want that), so?
create table foo( value text, constraint uk unique( value ) );
begin
> On Mar 18, 2015, at 9:11 PM, Jason Vas Dias
> wrote:
>
> am I missing something?
rollback?
> On Jan 8, 2015, at 7:21 PM, Lance Shipman wrote:
>
> Can SQLite support millisecond precision in date time data? I looking at doc
> I think so, but it's not clear.
There is no 'date time’ data type in SQLite. Feel free to store your time data
as either text or number. To
> On Jan 7, 2015, at 11:35 PM, Paul Sanderson
> wrote:
>
> Hmm - why can't I get that to work when the hex value is stored in a
> column, i.e.
Most likely your data is stored as text, e.g.:
with
DataSet
as
(
select '0x49962d2' as value
union all
select
> On Jan 7, 2015, at 11:08 PM, Paul Sanderson
> wrote:
>
> Is this possible?
With a contemporary version of SQLite, yes:
sqlite> select DateTime(77161170, 'unixepoch');
1972-06-12 01:39:30
sqlite> select DateTime(0x49962d2, 'unixepoch');
1972-06-12 01:39:30
> On Dec 21, 2014, at 10:47 AM, big stone wrote:
>
> - a minimal subset of analytic functions
+ MERGE! Yeah!
Happy Holidays!
___
sqlite-users mailing list
sqlite-users@sqlite.org
> On Dec 4, 2014, at 10:26 PM, Roger Binns wrote:
>
> That will only work under the simplest of cases.
Simplicity first and foremost.
___
sqlite-users mailing list
sqlite-users@sqlite.org
On Oct 8, 2014, at 8:51 PM, Stephen Chrzanowski wrote:
> If the field def'n were to be changed to [ col2 NUMBER DEFAULT ON NULL 0 ]
> and then when I insert/update something that becomes NULL and the result
> becomes 0 for that field, then yeah, bingo.
Yep, that’s exactly
On Oct 8, 2014, at 6:14 AM, Stephen Chrzanowski wrote:
> When adding a NULL value to a table that has the NOT NULL flag set on that
> field, instead of raising an exception, if the field definition were to
> have the word "USE" between "ON CONFLICT" and "DEFAULT" in its
On Sep 20, 2014, at 9:21 PM, Simon Slavin wrote:
> Anyone who worked for a big company these days and created such a database
> should get called in and told to do it again properly.
Along these same lines:
Your last name contains invalid characters
On Sep 16, 2014, at 8:15 PM, RSmith wrote:
> could you show how to achieve this in SQL via the ranking method you linked
Well, ranking is the same as numbering, no?
So, for example:
with
NameSet
as
(
select 1 as id, 'paul' as name union all
select 2 as id, 'helen'
On Sep 15, 2014, at 4:48 PM, Richard Hipp wrote:
> On Sun, Sep 14, 2014 at 12:18 AM, Lea Verou wrote:
>
>> Per the 3.7.11 changelog [1], queries of the form SELECT max(x), y FROM
>> table return the value of y from the same row that contains the maximum x
>>
On Sep 15, 2014, at 7:08 PM, Hick Gunter wrote:
> Maybe you can reformulate the query to fit
>
> INSERT OR UPDATE INTO t SELECT t.a,t.b,...,s.x,s.y FROM t, s …
There is no such a thing as 'INSERT OR UPDATE’ in SQLite. There is a ‘REPLACE’,
but it’s definitively not the same
On Sep 11, 2014, at 5:45 PM, Carlos A. Gorricho
wrote:
> Next step is to venture into XML - sqlite integration...both ways.
Considering you are on a *nix system, you may find Dan Egnor’s xml2 set of
command line utilities of interest:
On Sep 3, 2014, at 3:01 PM, Dominique Devienne wrote:
> Asked differently, if adding this support, could this be done by adding
> virtual / computed columns to tables, and indexing those columns?
Ohohohoho… virtual columns [1][2]…. yes… shinny! :)
Now that would be rather
On Sep 2, 2014, at 9:48 PM, jose isaias cabrera wrote:
> Thoughts? Thanks.
SQLite doesn’t have date per se. You are free to store dates as either text or
number, or anything you please. But it’s your responsibility to keep it
straight.
On Sep 1, 2014, at 9:19 PM, Keith Medcalf wrote:
>
>> On Sep 1, 2014, at 6:00 PM, Igor Tandetnik wrote:
>>
>>> (case when billdate != '' then billdate else bdate end)
>>
>> Or, more succinctly:
>>
>> coalesce( nullif( billdate, '' ), bdate )
>>
>>
On Sep 1, 2014, at 6:00 PM, Igor Tandetnik wrote:
> (case when billdate != '' then billdate else bdate end)
Or, more succinctly:
coalesce( nullif( billdate, ‘’ ), bdate )
(To OP: empty strings are E V I L. Don’t use them. Ever.)
On Aug 27, 2014, at 10:57 PM, Eduardo Morras wrote:
> Sorry, don't understand why others will throw an exception in the group by,
> perhaps I'm misunderstanding the group by, but that should work on others
> engines.
Because not all expressions are accounted for, i.e.:
On Aug 26, 2014, at 2:09 AM, Keith Medcalf wrote:
> select id, category_id, name, min(price) as minprice
>from cat_pictures
> group by category_id;
>
> Done. And no need for any windowing functions …
This peculiar behavior is very unique to SQLite. Most reasonable
1 - 100 of 625 matches
Mail list logo