Right, that's the bug we found. The statements are in the reverse order. It's
not quite that simple as the code below, but it ends up happening in that
order.
It's one of the most fundamental things a senior dev asks themselves on every
call that that differentiates them from a junior dev -
Fair enough. Agreed, just less of a chance (and we haven't seen it) because
Windows seems to provide more spacing between these values.
- Deon
-Original Message-
From: sqlite-users On Behalf Of
Warren Young
Sent: Tuesday, April 17, 2018
Yes, but the socket values differ by the thousands in Windows from handle
values returned by CreateFile.
On MAC they don't differ at all - it immediately gets re-used.
- Deon
-Original Message-
From: sqlite-users On Behalf Of
Peter Da
No problems with spam on my first day back on this list.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
On 4/17/18, Simon Slavin wrote:
>
> Can the list admins please take appropriate action ?
If you can identify the mailing list member that is sending the spam,
then I can banish them. But beyond that, what can I do? If somebody
is subscribed using email ab...@gmail.com,
On 17 Apr 2018, at 11:11pm, Rich Shepard wrote:
> FWIW, I haven't seen any spam from this mail list. I do run my own MTA
> which aggressively rejects known spam.
I won't give details in public but I will say that one or more characteristics
of the spam messages appear
On Tue, Apr 17, 2018 at 3:11 PM, Rich Shepard
wrote:
> On Tue, 17 Apr 2018, Simon Slavin wrote:
>
> Okay, that's enough. Thanks for the help, everyone.
>>
>
> Simon,
>
> FWIW, I haven't seen any spam from this mail list. I do run my own MTA
> which aggressively
On Tue, 17 Apr 2018, Simon Slavin wrote:
Okay, that's enough. Thanks for the help, everyone.
Simon,
FWIW, I haven't seen any spam from this mail list. I do run my own MTA
which aggressively rejects known spam. Over 20 years I doubt there have been
more than a handfull from all mail lists
> Le 17 avr. 2018 à 23:39, Simon Slavin a écrit :
>
> Are you getting a new dating-spam each time you post to this list ?
I indeed have got one minutes ago after my recent post here today. I was about
to write and ask about it here. :)
--
Best Regards, Meilleures
On 17 Apr 2018, at 11:00pm, Warren Young wrote:
> Yes. My recent reply to the header corruption thread triggered one.
I got a couple of direct email replies too, with enough information for me to
isolate the offending mail server.
Okay, that's enough. Thanks for the
having replied in this thread I got one.
(can the real simon slavin please stand up?)
On Tue, Apr 17, 2018 at 3:00 PM, Warren Young wrote:
> On Apr 17, 2018, at 3:39 PM, Simon Slavin wrote:
> >
> > Are you getting a new dating-spam each time you post
On Apr 17, 2018, at 3:39 PM, Simon Slavin wrote:
>
> Are you getting a new dating-spam each time you post to this list ? If you
> are, please post a brief follow-up to this message.
Yes. My recent reply to the header corruption thread triggered one.
This is not new:
march 26, apr 7 I found one each day in 'spam'
On Tue, Apr 17, 2018 at 2:39 PM, Simon Slavin wrote:
> Dear list-posters,
>
> Are you getting a new dating-spam each time you post to this list ? If
> you are, please post a brief follow-up to this message. Please do /not/
>
Martin wrote:
...
Example (maybe via .read):
.once .dat
select date('now');
.let f system echo "words-`cat .dat`.txt"
.once -let f
select word from words order by 1;
..
Sorry for replying only to this single point. The proposed ".let"
command is not
Dear list-posters,
Are you getting a new dating-spam each time you post to this list ? If you
are, please post a brief follow-up to this message. Please do /not/ include
any details about the spam, its headers, or the person it's apparently from.
Just a "me too" until I say I have seen
> Le 17 avr. 2018 à 22:07, Deon Brewis a écrit :
>
> closesocket(_socket); // posix socket
> SSL_shutdown(_ssl); // openssl (_ssl was initialized using the _socket above)
These two statements are inherently wrong, in this order. First you
SSL_shutdown(), then you
On Apr 17, 2018, at 2:07 PM, Deon Brewis wrote:
>
> One just has to be in the mindset that on unix based platforms, a socket is a
> file handle. (Not instinctive if you're coming from a Windows background).
You’re either using Winsock 1.1 or are dragging forward obsolete
On 17 Apr 2018, at 9:13pm, Peter Da Silva wrote:
> Even on Windows, wouldn't doing an ssl_shutdown on a socket you'd already
> closed still have a risk of unexpected behavior?
Under Windows an attempting to shutdown a connection which is already shutdown
returns
On 4/17/18, 3:08 PM, "sqlite-users on behalf of Deon Brewis"
wrote:
> So this was a special case of re-using the File handle as per the corruption
> guide. One just has to be in the mindset that on unix based
After months, I managed to track this down. I'd like to extend a BIG thanks to
Richard Hip and Dan Kennedy for their help in helping me instrument and
understand the SQLITE internal data structures better, as well as giving me a
way to programmatically do this, as well as to teach me about the
Hello Richard !
Now that you are making changes on sqlite3 parser could you please add
the table alias to delete/insert/update ?
I already have it working and got conflicts with the latest changes,
they are not big or complicated but it helps make some queries easier.
Cheers !
fossil diff
21 matches
Mail list logo