On 2014/11/26 15:58, Darko Volaric wrote:
I'm not looking for confirmation of ideas, on the contrary, people seem to want to push their own ideas about a database should be
used and how I'm not using it correctly, when that is irrlevent to the issue I'm discussing. Maybe more focus on the technical
facts and less on divining what I think at night in bed and try framing your arguments based on those technical facts rather than
ad-hominem attacks.
I am sincerely sorry if you construed my reply as anything remotely ad hominem - it surely wasn't, and it's not pushing ideas on
you, it's giving advice or alternates because your ideas are short-sighted and hard to implement. We are however very nice on here
since sharing knowledge is a passion, and that's why we say nice things like we understand how it feels to have ideas and then offer
some advice... not because we spend our days divining about your life. You throw everyone's advice back in their faces and are
arrogant about it - well, even to that we are still nice and willing to answer the questions - kindly accept it in that spirit.
But I don't intend to argue this point any further since I'm merely looking for advice about how the database engine is
implemented, not about how it's used or how I'm using it.
Ok, sticking to the facts, the database engine is implemented in a way that
makes your original suggested options pan out like this:
1 - very easy for the engine, very work intensive for you.
2 - still easy for the engine, although it will lose most RDBMS querying value, and still cumbersome for you (Maybe best to use
Virtual tables to implement this), and
3 - impossible without a dedicated fork, and even then very difficult.
I wouldn't personally pick any of those, but if those were the only options in life and I had to pick one, knowing SQLite, I'd
probably lean more towards option 2 than the others.
SQLite is "loosely typed", but it is still typed, and the typing mechanism is not open to the API and every one of the hundreds of
core functions in SQLite are specifically coded to dance with those few primary types. Adding/Altering it must always be the very
last option on any list.
Good luck,
Ryan
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
