Hayden, I've been following your questions (to try and help) but I have to comment - the questions are all exceedingly vague, it's really hard to help with one hand tied behind our collective backs.
This is not a complaint - I'm very sure you try to keep it short out of kindness and consideration (not wanting to be a bother etc.), but you trim the questions beyond comprehension. If the question regards performance, for instance, please post a schema or some SQL that shows the problem. I know in your mind it "makes sense" when you describe the situation, but it is extremely hard for us (who have no insight into the dev environment) to follow exactly what is meant, plus the fact that what you imagine might cause the problem may or may not be the actual thing, so if not mentioning the other things that might be involved, we have to guess, and as you have (no doubt) noticed from many of the replies - we often guess very wrong. On 2015-07-18 07:37 AM, Hayden Livingston wrote: > I was getting garble in my SQLite database, so I switched > PRAGMA=UTF-16 on for my INSERT statements. These are getting prepared. > > I noticed my total time dramatically increased. > > I then switched to UTF-8 thinking it's the increased writes causing > it, no noticeable difference, i.e. it's just as slow as PRAGMA=UTF-16. > > Removing PRAGMA from my INSERT statements brings back the performance. > > Any ideas? A case in point, this latest question - there are so many things that influence speed to do with encodings, such as custom collations, is this table FTS or not?, What garble did you get?, Encoding cannot ever be changed for any SQLite DB, so when you say you "switch" it, what do you mean? The DB only ever stores bytes, so any retardation is likely during conversion. A simple bit of SQL script / schemata will answer all these and remove any guesswork.
