hello brian, what standars? reading deeply the sqlite site i not see the
@issue buton@
only see that all contact way must be in the mail list... its a 21 century
and ID urls its the standar way of integration...
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
2017-06-07 12:12
Wanted to just let you all know that I really appreciated the help you offered
when I asked this a few months ago.
Since then, I've jettisoned the idea of using multiple threads and moved to
using multiple processes instead. I have built out an API that accepts http
requests for queries,
On 7 Jun 2017, at 1:49pm, Daniel Polski wrote:
> Ok, have I understood this correctly:
>
> If doing a manual checkpoint with SQLITE_CHECKPOINT_TRUNCATE, that call will
> block for maximum the time set by the busy_timeout while trying to proceed.
> If the busy timeout
Not exactly.
You're free to extend it yourself and submit it for consideration though. I
think that you'll just need to adopt the same standards as are in use
within the usual enhancements channels.
Regards.
Brian P Curley
On Wed, Jun 7, 2017 at 12:09 PM, PICCORO McKAY Lenz
Why should Richard and other devs rely on something other than their own
work and source control? You can't be 100% certain that GitHub is going to
be online tomorrow, which means that a scramble to push code to another
site is going to happen. You can't be certain that whatever comes after
2017-06-07 9:59 GMT-04:00 Richard Hipp :
> I would suggest, then, that you grab a copy of the SQLite source code,
> put it on github, and start your own fork. You can then add whatever
> new SQL commands you want.
>
> At this point, your chances of getting us to do your work for
They're using Fossil as the repository. You'll want to confirm the steps
required, but the main access point is as follow (I believe):
https://www.sqlite.org/src/login
The main concern is that the functionality that you seek might not scale to
the broader user base. You can always extend it
Patches are still welcome, I guess. I haven't seen anybody claiming
that this would be done in any way.
On 6 June 2017 at 15:17, PICCORO McKAY Lenz wrote:
> how its the status of this work?
>
> a limited implementation will be good!
>
> Lenz McKAY Gerardo (PICCORO)
>
On Jun 7, 2017, at 10:37 AM, Stephen Chrzanowski wrote:
>
> You can't be 100% certain that GitHub is going to
> be online tomorrow
As well, we have plenty of history showing that we can’t trust the long-term
availability or trustworthiness of third party hosting services.
Den 2017-06-07 kl. 17:09, skrev Simon Slavin:
On 7 Jun 2017, at 1:49pm, Daniel Polski wrote:
Ok, have I understood this correctly:
If doing a manual checkpoint with SQLITE_CHECKPOINT_TRUNCATE, that call will
block for maximum the time set by the busy_timeout while
On 6 Jun 2017, at 2:17pm, PICCORO McKAY Lenz wrote:
> how its the status of this work?
The work of parsing comments in the CREATE TABLE command ? I don’t think
anyone else thinks this is worth working on. Discussion in this list has come
up with many reasons why
Hi Andrew,
This is a great use case for SQLite. Did you have to use any special flags or
settings for SQLite to achieve this e.g. cache size, page size Read only etc?
Thanks,
Vikas
> On Jun 7, 2017, at 10:07 AM, Andrew Brown
> wrote:
>
> Wanted to just
ipost github as example.. there a sourceforge git capabilities over large
years.. also You can't be 100% certain that Ricahd resources is going to
be online tomorrow.. sf.net, github, gitlab and googlecode are still only
voer many years... and all of them works with openid...
for Stephen
2017-06-07 13:57 GMT-04:00 Simon Slavin :
> The work of parsing comments in the CREATE TABLE command ? I don’t think
> anyone else thinks this is worth working on. Discussion in this list has
> come up with many reasons why it’s a poor way to store comments, including
>
Although I had experimented with this at great length while I was still running
a multithreaded model, after switching to the multi process model, I did some
minor experimentation but it was already extremely fast and it didn't show
significant gains. Going forward I do intend to experiment
Den 2017-06-05 kl. 17:48, skrev Simon Slavin:
On 5 Jun 2017, at 1:45pm, Daniel Polski wrote:
How do I make the checkpointing work like the above documentation describes?
Set a timeout. Perhaps a very long one (one minute, which is what I use in
some places). You
On 6/7/17, Daniel Polski wrote:
> Does the [TRUNCATE] checkpoint call lock out new requests which might prohibit
> checkpoint progress while waiting for the timeout?
It prohibits new writers. New readers are allowed to proceed.
> What will happen with other connections
the problem its that for making some noise or request users must
register, send email, waith response aproval.. too complicated
processs.. that's the reason
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
2017-06-07 2:16 GMT-04:00 Daniel Kamil Kozar :
> Patches
Hello guys,
First of all, thanks for your great work, I really appreciate working
with SQLite. I've recently found a minor typo in
https://sqlite.org/fileformat2.html#sqlite_stat2 in the last row, where
it states "it is exists, is simply ignored", maybe it should state "if
it exists, is simply
On 6/7/17, Daniel Polski wrote:
>
>
> Den 2017-06-07 kl. 15:02, skrev Richard Hipp:
>> On 6/7/17, Daniel Polski wrote:
>>> Does the [TRUNCATE] checkpoint call lock out new requests which might
>>> prohibit
>>> checkpoint progress while waiting for
the github issue tracker are more easy to send.. register can made with any
openid service.. no a complicated email out/of/time system.. its the 21
century men
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
2017-06-07 9:24 GMT-04:00 Stephen Chrzanowski :
>
On 6/7/17, PICCORO McKAY Lenz wrote:
> the github issue tracker are more easy to send.. register can made with any
> openid service.. no a complicated email out/of/time system.. its the 21
> century men
I would suggest, then, that you grab a copy of the SQLite source
What other way would there be? Just anonymous "Fix it, add this, do it
now!" kind of messages? If you don't register, then anyone can start
spamming the hell outta the message board.
On Wed, Jun 7, 2017 at 9:15 AM, PICCORO McKAY Lenz
wrote:
> the problem its that for
Den 2017-06-07 kl. 15:02, skrev Richard Hipp:
On 6/7/17, Daniel Polski wrote:
Does the [TRUNCATE] checkpoint call lock out new requests which might prohibit
checkpoint progress while waiting for the timeout?
It prohibits new writers. New readers are allowed to
Fixed. Thanks.
On 6/6/17, Leon Höpfl wrote:
> Hello guys,
> First of all, thanks for your great work, I really appreciate working
> with SQLite. I've recently found a minor typo in
> https://sqlite.org/fileformat2.html#sqlite_stat2 in the last row, where
> it states "it
25 matches
Mail list logo