On 24 Aug 2009, at 4:22am, Tito Ciuro wrote: > But that would introduce the overhead of doubling the space required > for every string + an additional column index.
One of the options I mentioned was to store the reversed string and not the original. If you need to reconstruct the original string, read the reversed one and reverse it your software. Will you actually be short on space ? If you're programming for an embedded platform then I can understand space is a concern. If you're using a standard desktop computer and your database doesn't have millions of records it might not be. By all means, work to your priorities. > If the schema contains > more columns where this type of query needs to take place, it seems to > me that this would not be a good solution. 'good' relative to what ? I'm always interested in better solutions. Simon. PS: new text /below/ quoted text please. If you don't thing readers need to read the original text, there's no need to include it at all. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
