I'm on my second day of porting SQLite to an embedded
environment. I'm not sure if this is the appropriate
place to put these comments about the experience.
I've seen some type of "ticket" mechanism in CVS but I
don't know if these comments raise to the level of a
"bug", etc.
Anyway, three
I'm still pretty new to sqlite but have written a few
test programs over the last month and gotten everthing
working well. For small-to-medium sized tables, the
performance is great - this is a wonderful tool to use
for large and complex application files, especially
ones where there is variable
--- Andrew Piskorski <[EMAIL PROTECTED]> wrote:
> That seems bizarre. Typical RDBMS practice would be
> to just use a
> two-column composite primary key.
>
>
> Did you measure a serious performance problem when
> joining on two
> separate columns?
>
You're right. It feels bizarre to me too.
I have two questions. I'm starting a large project
with SQLite on multiple platforms. I'm hoping I can
get some ideas about two issues:
1. Is numeric column storage maintained in an
endian-independent way? I need to port SQLite to a
platform that is in Motorola format (big endian) but
haven't
4 matches
Mail list logo
