Hi there,
I have used sqlite to store parameter changes with a time stamp in a simulation
environment.
Because of the number of parameters (2000+) and the max. change rate up to 50ms
I have a separate table for each parameter with time stamp and value.
The time stamp is used as "integer
Zaumseil Ren? wrote:
> I have a separate table for each parameter with time stamp and value.
> The time stamp is used as "integer primary key asc".
> [...]
> It is also possible to go back in time and then start from there.
> Currently I remove all values from the tables after the specified time.
Ad 1)
You may be able to speed up deletion if you can partition your logging tables
by time, e.g. each table holds the changes within a certain time frame or a
fixed number of changes.
When you jump back in time, dropping the tables created after the target
timestamp is faster than deleting
Some suggestions:
1) Check your temp folder and remove chaff.
2) Download CCleaner and check your registry integrity.
3) Review updates that have been applied and try removing them one at a time
or in a targeted fashion. You should be able to see what updates were
applied around the time you
Ryan, Simon, thank you both for the help.
The script works fine, and I now also understand how to use this bail
mechanism. It is great!
once more: THANK YOU!
gert
2015-04-01 23:17 GMT+02:00 Simon Slavin :
>
> On 1 Apr 2015, at 8:09pm, Gert Van Assche wrote:
>
> > But this is definitely not
On Wed, 1 Apr 2015 14:26:15 -0700, Mark Romero wrote:
> Thank you all for all your help.
>
> I have been soliciting advice from all sorts of Lightroom forums / adobe
> forums / Dell computer forums and other forums more specific to hardware
> and Lightroom, and they all ended up in a dead end.
>
SQLite version 3.8.9 is now in testing. When the status board at
https://www.sqlite.org/checklists/3080900/index goes all green, we
will cut the release. If you have any concerns about the current
code, please speak up soon!
A draft of the 3.8.9 website is found at http://www.sqlite.org/draft/
2015-04-02 15:15 GMT+02:00 Richard Hipp :
> A draft of the 3.8.9 website is found at http://www.sqlite.org/draft/
> and in particular the change log can be seen at
> https://www.sqlite.org/draft/releaselog/3_8_9.html
I would have expected to find this change somewhere in the
release log:
Hi Everyone,
I am new here, and have a question.
For my application that relies on Sqlite I am seeking Windows 8 certification
in accordance with the following article.
[ https://msdn.microsoft.com/en-us/windows/desktop/hh749939.aspx ](
On 4/2/15, maarten.mostert at stakepoint.com
wrote:
>
> Hi Everyone,
>
> I am new here, and have a question.
>
> For my application that relies on Sqlite I am seeking Windows 8
> certification in accordance with the following article.
>
> [
Thank you Kess for the suggestions:
Number of photos per directory: I tried this but it seems to have had no
benefit. i went from 200 photos in one directory down to 50 photos in four
directories, and there was no change.
I will try your other suggestions (disable automatic re-catalogging and
Please find here under the test results.
Best regards,
Maarten MOSTERT
28 Av Alphonse Denis
83400 Hy?res, France
+33 676411296
[ http://stakepoint.com/ ]( http://stakepoint.com/ )
==
Windows App Certification Kit - Test Results
Windows App
On 4/2/15, maarten.mostert at stakepoint.com
wrote:
>
> WARNING
> Binary analyzer
> Warning: The binary analyzer test detected the following errors:
> File C:\Program Files\StakePoint\sqlite3.dll has failed the NXCheck check.
> File C:\Program Files\StakePoint\sqlite3.dll has failed the DBCheck
This are basically compiler switches as far as I understand.
I am not a C programmer, so also quite difficult for me to link the library
statically.
This is what I can read about it here:
[
https://msdn.microsoft.com/en-us/library/windows/apps/jj657973.aspx#binscope_2
](
On Thu, Apr 2, 2015 at 10:58 AM, wrote:
>
> This are basically compiler switches as far as I understand.
>
> I am not a C programmer, so also quite difficult for me to link the library
> statically.
These tests basically map to the /SAFESEH, /DYNAMICBASE, and /NXCOMPAT
linker flags. Though,
On 4/2/15, Random Coder wrote:
>
> I'd recommend the SQLite team turn them on for the version of the DLL
> they distribute, but I'm honestly not sure if there are negative side
> effects to doing so.
That's not possible, unfortunately, We compile the published DLL
(the 32-bit DLL at least)
HI,
If I may...
On Thu, Apr 2, 2015 at 4:25 PM, Richard Hipp wrote:
> On 4/2/15, Random Coder wrote:
>>
>> I'd recommend the SQLite team turn them on for the version of the DLL
>> they distribute, but I'm honestly not sure if there are negative side
>> effects to doing so.
>
> That's not
add the following linker options with MinGW:
-static-libgcc -Wl,-Bstatic,--nxcompat,--dynamicbase,--export-all-symbols
You may or may not need -static-libgcc or the linker -Bstatic options unless
you are also enabling things that require MingW DLL runtime support (such as
using the -mthreads
BTW, I have verified that these options all work as described and the options
are recognized and processed properly by Windows, and that BinScope is happy:
Failed checks
d:\source\sqlite\sqlite3.dll - SafeSEHCheck ( FAIL )
Passed checks
d:\source\sqlite\sqlite3.dll - NXCheck ( PASS )
I hate correcting myself. You do not need the --export-all-symbols
Using it will cause all non-static symbols to be exported (even without a
specific dllexport) just like using -shared on unices.
---
Theory is when you know everything but nothing works. Practice is when
everything works but
20 matches
Mail list logo