On Mon, Nov 12, 2012 at 1:52 PM, Doug Nebeker wrote:
> You might be surprised at the speed increase you see in compile time if
> you've got large projects. The time isn't lost to CPU as much, but disk I/O
> time adds up when hitting many hundreds of small (header) files (even with
> an SSD).
>
T
The application in question is a Windows desktop application, however,
storing the data is typically stored remotely for proper backup
procedures. I don't have control over where the files are stored, as this
is an IT decision for the companies in question, and the software allows
for users to sto
You might be surprised at the speed increase you see in compile time if
you've got large projects. The time isn't lost to CPU as much, but disk I/O
time adds up when hitting many hundreds of small (header) files (even with
an SSD).
Doug
-Original Message-
From: sqlite-users-boun...@sqlit
I always turn pre-compiled headers off for every VC++ project. In my opinion,
they are artifacts from a time when processors were a few hundred times slower
than they are now. The benefit in time saved now is far less than the
confusion they cause when something goes wrong.
RobR
-Origina
On 12 Nov 2012, at 7:15pm, Stephen Chrzanowski wrote:
> I *KNOW* doing transactional work (Even just standard selects) can cause
> problems via a network share with SQLite due to networking `bugs` or
> whatever. My question is, does/would the backup api have the same problem
> if I were to back
I *KNOW* doing transactional work (Even just standard selects) can cause
problems via a network share with SQLite due to networking `bugs` or
whatever. My question is, does/would the backup api have the same problem
if I were to backup a remote file to memory or local storage, work on data
locally
It isn't VS2010 specific. Even going back to VS6 writing your own C++
wrapper and including the.c file you had to tell it to not use
precompiled headers for that file. (Both Debug and Release builds)
You should tell VS that this file will not ever be using precompiled headers.
On VS2012 Professio
>> I know this question is not a SQLite question, but I am hoping that
>> someone here has had a similar experience and/or can point me to the right
>> place to ask this question.
>>
>> After years or using Code::Blocks and Dev-Cpp, I have recently installed
>> Visual Studio 10 Express; it is the f
Quoting Igor Tandetnik :
stahl...@dbs.uni-hannover.de wrote:
SQLite's behavior makes sense, because *every* column type may be left out.
However, I think that in the case of FK-definitions (like the one in 'tab2')
assigning the default type is not the right thing to do.
Why should one clause
Remove "use precompiled header" from your configuration.
On 10 November 2012 14:11, Arbol One wrote:
> I know this question is not a SQLite question, but I am hoping that
> someone here has had a similar experience and/or can point me to the right
> place to ask this question.
>
> After years
Daniel Polski wrote:
> Clemens Ladisch skrev 2012-11-09 17:00:
>> SELECT 'SELECT units.id AS "unit id"' AS SQL
>> UNION ALL
>> SELECT ', cv' || id || '.value AS ' || quote(name) FROM configtypes
>> UNION ALL
>> SELECT 'FROM units JOIN unit_types ON units.unit_type_id = unit_types.id'
>> UNION ALL
>
On 12 Nov 2012, at 7:54am, Darren Spruell wrote:
> If I'm not mistaken, that's a problem too, as type definitions are
> ignored on FTS columns:
Oh. You're trying to mess with a table used in an FTS definition. Okay.
Don't do that unless you understand how FTS works.
By all means define for
Simon Slavin skrev 2012-11-09 17:32:
In answer to the original query, my instinct is to say that you should be using
your own software to collect the results of several SELECTs, not trying to do
everything inside a database engine.
That's an interesting point. I still think it's the most suit
Clemens Ladisch skrev 2012-11-09 17:00:
Thanks alot for the help! :)
Are you sure that the normalization hasn't gone a *little* bit too far?
Yes, it makes perfect sense in other parts of the application.
FOREIGN KEY( unit_id ) REFERENCES unit_types ( id )
Why is this column not called unit
14 matches
Mail list logo
