He's wrong.  And "computers" don't start at 0.  It's up to the
compiler/interpreter to decide what the first index is.  In Cold Fusion, the
first index is always 1.

--
Mosh Teitelbaum
evoch, LLC
Tel: (301) 625-9191
Fax: (301) 933-3651
Email: [EMAIL PROTECTED]
WWW: http://www.evoch.com/


> -----Original Message-----
> From: Tom Sammons [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 01, 2002 5:09 PM
> To: CF-Talk
> Subject: CFQUERY and STARTROW=0 (??!)
>
>
> Hi all,
>
> I was looking up some stuff on joins versus unions, and came across an
> opinion that used CFQUERY as an example. (I won't post the url since I
> don't know if it's kosher here.)
>
> However, under this person's tutorial topic called "Limiting Results" it
> used this code:
>
> <CFQUERY DATASOURCE = "Friends" Name = "Query1" Maxrows = "10" Startrow
> = "0">
>
> followed by the comment:
>
> "Note that the starting row is set at 0. Remember that computers start
> numbering at 0, not 1.
> So the first record in the database is record number 0."
>
> -------
>
> Now, I understand offsets, et cetera, but I've never heard it used
> regarding cfquery (or any other sql query for that matter -- I couldn't
> even find another mention of startrow=0 anywhere in google or
> altavista for any major sql platform...).
>
> And obviously, I've never had a problem with using startrow=1 missing
> the first record of a query return set.
>
> Has anyone else ever used startrow=0 in *any* sql platform, is it
> practical/standardized, or is this guy just telling people to do things
> the
> way he thinks they should be?
>
> Inquiring minds (at least one) want to know...
>
> Tom
> 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
This list and all House of Fusion resources hosted by CFHosting.com. The place for 
dependable ColdFusion Hosting.

Reply via email to