On 10/28/10 8:25 PM, "Bob Sneidar" <b...@twft.com> wrote: > Really, this is so limiting that it may be better to dump your database, > recreate the new structure, and then re-import it, or do the second database > thingummy, rather than try to modify the schema.
Right. Modification of schema is pain ... And it was for years for many dbs. E.g. I remember that 4D was not able also remove column from Table. I remember that old good dbVista (network model) also was not able modify links Once dbVista expert user have to see Valentina db with its API -way (i.e. NON-SQL) and said: wow! Valentina is like dbVista in many aspects but can modify anything. ** you can more or less easy massage db data if this is single db on your computer. But what you will do if your Application (made with REV/LiveCode/...) have embedded db engine and should be able modify exists hundreds users dbs on their side without you, when they get v2 version of APP. > And I looked up the limits in sqLite. Apparently the original idea was to have > no limits, but people found that when you push sqLite to extremes, issues > begin to crop up and security can break down. There are however, so far as I > have been able to tell, no record limits for sqLite. I think it is more accurate to say in theory it is possible to have ULONG (2^32 = 2 billions) records. -- Best regards, Ruslan Zasukhin VP Engineering and New Technology Paradigma Software, Inc Valentina - Joining Worlds of Information http://www.paradigmasoft.com [I feel the need: the need for speed] _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution