On Wed, 1 May 2019 at 19:30, Frank Kemmer wrote:
>
> https://github.com/xerial/sqlite-jdbc/blob/14839bae0ceedff805f9cda35f5e52db8c4eea88/src/main/java/org/sqlite/core/CoreResultSet.java#L86
>
> Here we see, that colsMeta == null results in throwing the seen exception.
>
> But how can colsMeta be
Yes, this will work. It's a long story. I am creating a Gantt visual schedule
of a project based on the tasks dates, and I want to show the visual effects
per weeks. But, you have hit the hammer on the nail, as we say in Spanish.
This I can use.
Donald Griggs, Thursday, May 2, 2019 04:16
I found this very interesting,
15:52:46.71>sqlite3
SQLite version 3.28.0 2019-04-16 19:49:53
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> SELECT strftime('%W','2019-01-01');
00
sqlite> SELECT
Hello Jose,
Regarding: "...but I need to get the week of that month based on the date."
One interpretation of your question might me:
Given a date "d", which, say, falls on a Wednesday, then return
1, 2, 3, 4, or 5 denoting whether d is on the 1st, 2nd, 3rd, 4th, or
5th Wednesday of that
Ok I understand now.
It was difficult to see why SQLite would ever choose to return rows in a
different order than the order in which they were stored if the SELECT does not
specify an ORDER until Dr. Hipp explained that it could get the requested
columns from a separate index instead of the
I think "week of the month" is not a standard value. As with week of the year,
is week #1 the week in which the month starts, the first complete week within
the month, or the first week with at least 4 days?
- Original Message -
From: Jose Isaias Cabrera
To:
Greetings.
To break Manuel's constant bug finding emails, :-), I want to get the week of
the month from either date or strftime functions. I know I can get the week of
the year by doing,
SELECT strftime('%W','2019-03-07');
but I need to get the week of that month based on the date. I can
Hi everyone,
I found another corner case where I could break an index on a REAL column
(UNIQUE constraint failed: index 'index_0').
CREATE TABLE test (c0 REAL);
CREATE UNIQUE INDEX index_0 ON test(TRIM(('' * c0)));
INSERT INTO test(c0) VALUES (0.0), (0.1);
REINDEX;
As with the previous
Thanks a lot!
Best,
Manuel
On Thu, May 2, 2019 at 7:52 PM Richard Hipp wrote:
> On 5/2/19, Manuel Rigger wrote:
> > Hi everyone,
> >
> > I think that I found another issue related to type affinity on real
> columns:
>
> The typeof() function corner-case you identified has been fixed in
>
On 5/2/19, Manuel Rigger wrote:
> Hi everyone,
>
> I think that I found another issue related to type affinity on real columns:
The typeof() function corner-case you identified has been fixed in
check-in https://www.sqlite.org/src/timeline?c=48889530a9de22fe
--
D. Richard Hipp
d...@sqlite.org
Great, thanks!
Best,
Manuel
On Thu, May 2, 2019 at 6:25 PM Richard Hipp wrote:
> Documentation has been updated in an attempt to clarify when UPSERT
> applies and when it does not.
>
> On 5/2/19, Manuel Rigger wrote:
> > Okay, thanks for the clarification!
> >
> > I think that this part of
Documentation has been updated in an attempt to clarify when UPSERT
applies and when it does not.
On 5/2/19, Manuel Rigger wrote:
> Okay, thanks for the clarification!
>
> I think that this part of the documentation is ambiguous. The part of the
> documentation that you quoted mentions a
Hi everyone,
I think that I found another issue related to type affinity on real columns:
CREATE TABLE test (c0 REAL);
CREATE UNIQUE INDEX index_0 ON test(TYPEOF(c0));
INSERT OR IGNORE INTO test(c0) VALUES (0.1);
INSERT OR IGNORE INTO test(c0) VALUES (FALSE);
REINDEX;
In this example, the
Okay, thanks for the clarification!
I think that this part of the documentation is ambiguous. The part of the
documentation that you quoted mentions a "conflict target", but there is no
conflict target in the example that I provided. The documentation
continues by stating that a conflict target
On 5/2/19, Manuel Rigger wrote:
> Hi everyone,
>
> It seems that upsert does not take into account "NOT NULL" constraints. In
> the example below, I get an error "NOT NULL constraint failed: test.c0":
>
> CREATE TABLE test (c0 NOT NULL);
> INSERT INTO test(c0) VALUES (NULL) ON CONFLICT DO
Hi everyone,
It seems that upsert does not take into account "NOT NULL" constraints. In
the example below, I get an error "NOT NULL constraint failed: test.c0":
CREATE TABLE test (c0 NOT NULL);
INSERT INTO test(c0) VALUES (NULL) ON CONFLICT DO NOTHING;
I would have expected that the second
This mailing list disallows attachments as a anti-spam measure. You
can send attachments directly to me, if you like.
On 5/1/19, Stephen Hunt wrote:
> Hi,
>
> We use SQLite extensively here at Zaber and are quite pleased with it.
> However, we recently added a view that incorrectly returns
Fixed at https://www.sqlite.org/src/timeline?c=b043a54c3de54b28
On 5/1/19, Manuel Rigger wrote:
> I'm very sorry, after finding the issue using the latest stable Linux
> version, I accidentally used an outdated version (3.24.0) to produce a
> minimal failing case. Here is a reduced example that
@Warren: I'm building a tool to test DBMS by automatically generating
queries and checking their results. Since the statement sequence was
generated automatically, it looks like artificial.
@Keith Thanks again for the explanation!
Best,
Manuel
On Thu, May 2, 2019 at 1:24 AM Keith Medcalf
19 matches
Mail list logo
