y
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smart Software Solutions GmbH
Dipl.-Inf. Markus Schaber | Product Development Core Technology
Memminger Str. 151 | 87439 Kempten | Germany
Tel. +49-831-54031-979 | Fax +49-831
ent from
> returning an error at function-level.
An Exception in the SQL sense effectively results in an errorcode returned by
an sqlite function.
SQLite is implemented in C, there are no exceptions on the language level it
could raise.
Best regards
Markus Schaber
CODESYS(r) a trademark of
com/Division-by-zero-td1922266.html
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smart Software Solutions GmbH
Dipl.-Inf. Markus Schaber | Product Development Core Technology
Memminger Str. 151 | 87439 Kempten | Germ
esponding CREATE TABLE statements
may be faster, depending on your I/O system, as it can fetch the table contents
from RAM during index creation.
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smart Software Solut
atabases in my former jobs, I
strongly suggest that you consider PostgreSQL before considering MySQL. :-)
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smart Software Solutions GmbH
Dipl.-Inf. Markus Schaber | Pro
rs adopted the syntax 0o123 for octal literals.
The IEC 61131 languages use the syntax base#value, so 16#12ab is a hex number,
and 8#123 is an octal number.
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smart Software S
On the other hand, PostgreSQL
has built-in "decimal" and "numeric" types which allow up to 131072 digits
before and 16383 digits after the decimal point.
http://www.postgresql.org/docs/current/static/datatype-numeric.html
So one might argue such datatypes could also fit we
> errors for oversized hex literals in that context.
> >
>
> +1. --DD
I'm also in favour of (6) for now.
This still leaves room for upwards compatible behavior should SQLite
(version 4, maybe) or an extension add support for larger integers.
Best regards
Markus Schaber
C
ly depends on your data format and parser code.
The author of http://sebastianraschka.com/Articles/sqlite3_database.html#results
claims a factor ~20 speed advantage for SQLite.
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S
column, and the table will be pre-ordered by said value.
But be sure you read the caveats in the documentation before proceeding.
https://www.sqlite.org/withoutrowid.html
https://www.sqlite.org/lang_createtable.html#rowid
I'm also not sure how this affects insertion time, but if the value is growing
mo
or backwards compatibility reasons.
> > (WAL is another example of that.)
>
>
> Agreed. Backward compatibility would be a problem for SQLite3 so it's not
> going to happen either way unless the file format is revised and more PRAGMAs
> added. Maybe in SQLite4.
Best regards
Marku
eate such linkage with C#, maybe
some postprocessing is necessary.
On the other hand, SharpSVN also links a lot of native code directly into the
DLL - using C++/CLI instead of C#, this is rather easy.
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
sn't going to disappear
> tomorrow.
I doubt that _all_ those machines exclusively run on parity-enabled RAID
levels, but I'm strongly interested in a proof of your "fact" here.
I remember reading that PostgreSQL and Oracle recommend using mirroring based
levels instead of parity-en
Hi,
Von: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org]
> On 3 Mar 2014, at 8:18am, Markus Schaber <m.scha...@codesys.com> wrote:
> > Another way to bust your data is to rely on RAID 5 or 6 or similar, at
> > least if the software does not take speci
id time window, and the third disk fails, it's content
will be restored using the new data block and the old checksum (or vice
versa), leaving your data garbled.
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smart Softw
C source, it is independent of the CPU.
If your OS or runtime environment is not yet supported, you can create your own
platform abstraction layer.
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smart Software Solutions
Hi, Jason,
It might be that this is a little bit to big for sqLITE.
Maybe a "big iron" database like PostgreSQL or the Greenplum Database will fit
your requirements better.
Best regards
Markus Schaber
CODESYS® a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation
nux.
I'd prefer to use relative pathes with a normalized '/' or '\' within the
database, and store the base directory somewhere else (or maybe define the
pathes relative to the location of the sqlite database).
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solu
Hi, Simon,
von Simon Slavin
> On 4 Sep 2013, at 3:05pm, Markus Schaber <m.scha...@codesys.com>
> wrote:
>
> > Afaics, this applies to partial indices for similar reasons.
>
> I did not even know partial indices was implemented. Thank you.
It's new in 3.8.0 :-)
B
d it does mean that earlier and later versions of
> SQLite won't play nice under some circumstances.
Afaics, this applies to partial indices for similar reasons.
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smar
It's all
> on a one laptop.
Just to be safe: Can you roule out any antivirus or other security software
locking the files temporarily?
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smart Software Solutions GmbH
ing_Mono
http://docs.oracle.com/javase/1.5.0/docs/guide/jni/spec/invocation.html
http://gcc.gnu.org/onlinedocs/gcc-4.0.3/gcj/Invocation.html#Invocation
There are other interoperability mechanisms available - e. G. CORBA, or on
Windows, one could use COM.
Best regards
Markus Schaber
COD
ther sequence of those 3 steps (vacuum, indexing, moving to
> storage)
Did you consider running ANALYZE, too? That will populate the statistics which
the query planner can use to gain optimal index usage.
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutio
Hi, Richard,
Von Richard Hipp
> On Mon, Aug 26, 2013 at 10:39 AM, Markus Schaber <m.scha...@codesys.com>wrote:
> > Having a closer look, this will only solve problems with pathes whose
> > UTF8-encoding is longer than MAX_PATH bytes, but not with pathes which
> > exc
AX_PATH bytes, but not with pathes which exceed
the 260 character limit.
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smart Software Solutions GmbH
Dipl.-Inf. Markus Schaber | Product Development Core Technology
Memmi
Hi, Richard,
Von: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org]
> On Thu, Aug 22, 2013 at 10:38 AM, Markus Schaber <m.scha...@codesys.com>wrote:
> > During our internal tests, I recently stumbled across a problem when
> > using SVN, which
m already on contact with the SVN Developers, but I think the
issue is best fixed in SQLite itself:
http://svn.haxx.se/dev/archive-2013-08/0344.shtml
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smart Software Solutions Gm
27 matches
Mail list logo