On 5 April 2017 at 21:37, Scott Robison wrote:
> bash supports a --posix switch, which makes it more POSIX-compliant. It
> also tries to mimic POSIX if invoked as sh.
>
And while these methods ensure _compatibility_ with POSIX scripts, they
don't ensure that all executed scripts are POSIX compli
Looks like the .lint command has been in since 3.16.0, but this is my first
time noticing it and trying it out. I ran the .lint fkey-indexes on one of my
larger databases where I had thought I had indexed all the foreign keys ok, and
it spat out a giant swath of text, basically for every foreign
Thanks so much for looking into it!
- Deon
-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
Behalf Of Richard Hipp
Sent: Wednesday, April 5, 2017 7:30 AM
To: SQLite mailing list
Subject: Re: [sqlite] Expression Indexes - can I project the ex
On 4/5/17, Deon Brewis wrote:
> Hi,
>
> Just following up - is this tracked somewhere in a feature/bug database?
>
We are aware of the feature request and discussed it internally just
yesterday. It is non-trivial to implement.
--
D. Richard Hipp
d...@sqlite.org
_
Hi,
Just following up - is this tracked somewhere in a feature/bug database?
I have to do some interesting gymnastics to work around this all the time,
since the query optimizer seems to think it can read covered values from an
expression index, but during execution it doesn't.
e.g. On the ex
On Apr 5, 2017 7:28 AM, "Bob Friesenhahn"
wrote:
On Wed, 5 Apr 2017, Richard Hipp wrote:
>
> The deeper issue is that I do not have access to a machine that lacks
> bash on which to test the modifications
>
Specify the shell that configure will use like
CONFIG_SHELL=/bin/dash ./configure
On Wed, 5 Apr 2017, Richard Hipp wrote:
On 4/4/17, Jens Alfke wrote:
The issue here seems to be that some scripts in the SQLite source
distribution are _implicitly_ assuming that the default shell is bash, or
else that ‘sh’ is an alias of bash. The best fix, IMHO, would be to make
those scrip
On 05/04/2017 19:23, Richard Hipp wrote:
On 4/4/17, Jens Alfke wrote:
The issue here seems to be that some scripts in the SQLite source
distribution are _implicitly_ assuming that the default shell is bash, or
else that ‘sh’ is an alias of bash. The best fix, IMHO, would be to make
those scrip
On 3/31/17 6:08 AM, 邱朗 wrote:
Say my mobile app has a customer table, a product table, and an order table to
record who buys what, the order table basically has 2 foreign keys, customer_id
& product_id.
Now I got the order information first, within in it I can't find the customer information
On 5 April 2017 at 17:23, Richard Hipp wrote:
> On 4/4/17, Jens Alfke wrote:
> >
> > The issue here seems to be that some scripts in the SQLite source
> > distribution are _implicitly_ assuming that the default shell is bash, or
> > else that ‘sh’ is an alias of bash. The best fix, IMHO, would b
On 4/4/17, Jens Alfke wrote:
>
> The issue here seems to be that some scripts in the SQLite source
> distribution are _implicitly_ assuming that the default shell is bash, or
> else that ‘sh’ is an alias of bash. The best fix, IMHO, would be to make
> those scripts explicitly invoke bash, using a
Qiulang. I am curious about this requirement. Is there an example commerce
site in the real world where having a one to one match in a master customer
login table to all real customers is vital to the mission? What sort of
business would have that? Even banks do not have such surety about
custome
Thx, thats where i am headed
-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
Behalf Of Clemens Ladisch
Sent: Wednesday, April 05, 2017 9:53 AM
To: sqlite-users@mailinglists.sqlite.org
Subject: Re: [sqlite] recursive clause
Cem Dayanik (Ibtec
13 matches
Mail list logo