50% o well just have us an indication, nothing counted.
I meant 50% of this forum users, or... this planet, whatever.
All i meant is that sqlite is created by a c programmer, like my colleague
he seems to forget there are different languages but he doesn't care.
Well, to keep cdecl functions and provide examples with pointers is not
really a benefit to other kinds of users.
c is hard to read and/or convert for BASIC users, oops now i said it, BASIC
is often poison in c perspective :)
Well, i can not complain, sqlite is performing well and it's free.
But just wanted to make note to inform you there are other kind of
programmers in the world.
Wrapper libraries wouldn't not be necessary to access sqlite directly with a
little thought.
With my language i can safely access it, it's just all to much c imo.
The remark about the encrypted header is really a thing never experianced by
myself.
I don't think any fileformat supporting an encryption will also encrypt
these kinds of thing.
You are over-doing it imo.
I can imagne you want a totally safe file(format) this way.
But then, we are in disagreement :)
----- Original Message -----
From: "Dennis Jenkins" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, August 22, 2005 11:31 PM
Subject: Re: [sqlite] Why can i open a textfile?
Edwin Knoppert wrote:
Hmm, but every known file format has an header.
Sqlite has a string, not really a header as it seems.
Sqlite has a header. Part of it is plain text, part binary. You can
learn about it by reading the source code.
Maybe for v4 to implement a real header (if not yet)
A header doesn't need to be encrypted.
(A bit for testing if it's encrypted might have it use as well)
I very much disagree. I want the entire file, header included, to be
encrypted. Sometimes you don't want anyone to know what the file type is.
Security through obscurity is not secure. However, you don't want to give
the bad guys a road map either...
Sqlite seems to be created espec. for c programmers.
c programmers are truly a different breed :)
And we love it.
But it's not always handy to follow these directions or doings.
Iow, i never looked at the sqlite source how it works.
Sad, it is truely neat-o code.
I guess at least 50 percent over here does not really care and would
never explore how to solve these kind of things.
50 percent of whom? Programmers who use sqlite? Where is "over here"?
I hope examples and such will eventually get more polished towards other
languages as well.
Examples for instance show *sqlite as hstmt and there is really no use to
understand it's internally a pointer to a structure or so.
hstmt as Long would do.
Well long story but understanding functions (and even using it as cdecl)
is not that trival due conversion and such.
