On Thu, Oct 12, 2017 at 3:20 AM, Steve Holden <st...@holdenweb.com> wrote:
> The reason I liked "row" as a name is because it resembles "vector" and > hence is loosely assocaited with the concept of a tuple as well as being > familiar to database users. In fact the answer to a relational query was, I > believe, originally formally defined as a set of tuples. > > Is the intent that these things preserve order? in which case, I like row is OK (though still don't see what's wrong with record). I still dop'nt love it though -- it gives the expectation of a row in a data table )or csv file, or.. which will be a common use case, but really, it doesn't conceptually have anything to do with tabular data. in fact, one might want to store a bunch of these in, say, a 2D (or 3D) array, then row would be pretty weird.... I don't much like entity either -- it is either way to generic -- everyting is an entity! even less specific than "object". Or two specific (and incorrect) in the lexicon of particular domains. -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
