True enough. I have found however that if I operate on a set of basic principles, I develop habits which prevent problems later down the road. This is one of my principles, and it serves me well. I do not see any case where using special characters in an array key would give you an advantage over using simple text names. Of course, I don't see all ends. :-)
Bob On Apr 30, 2012, at 9:55 AM, Richard Gaskin wrote: > Bob Sneidar wrote: > > > Even you could use tabs in an array key, why would you want to? > > I cannot think of an application for this. I would stick to the > > same rules that SQL enforces for column names, and always use lower > > case, as SQL is sometimes case sensitive. That way you never shoot > > yourself in the foot if you ever want to translate from array keys > > to SQL column names. > > SQL is great for when you need relationality, but if there's anything we've > learned from the advent of the NoSQL movement it's that there are a nearly > infinite variety of ways to store data, so we no longer need to think in > terms of one-size-fits-all solutions. > > For example, in LiveCode small data sets can be handled with unusual grace > and easy as simple property sets in stack files. > > -- > Richard Gaskin > Fourth World > LiveCode training and consulting: http://www.fourthworld.com > Webzine for LiveCode developers: http://www.LiveCodeJournal.com > LiveCode Journal blog: http://LiveCodejournal.com/blog.irv > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
