I think one of the reasons that it's common for people to mistakenly use "it's" to mean the possessive (e.g., "go behind it's back") is because in most other contexts one is supposed to use an apostrophe to denote possession. For example: "go behind Bob's back" is correct. We get so used to using apostrophe + "s" to denote possession, it's a very understandable mistake to make.
On Sat, Mar 7, 2009 at 11:47 AM, Brian Kotek <[email protected]> wrote: > "Its" is a possessive pronoun that implies ownership. "It's" is a > contraction for "it is". It's the kind of thing that people who grew up with > English usually just "know" without really understanding why, if only from > lifelong experience with the language. In fact, it's kind of crazy how much > of the complexity of the English language people (or at least I) just know > on instinct rather than knowing the underlying grammar rules. > > In my case, it's almost always a simple typing mistake. I type by touch and > learned to type at a young age (one of the most valuable classes I took in > Jr. high, actually) so for me I rarely "think" about typing, but really just > talk in my head and let my fingers punch out the letters heh. So if I'm not > careful things like it's vs. its slip by. And of course the spellchecker > (another indispensable invention) can't catch things like that. > > Wow, this thread went OT in record time lol. > > On Fri, Mar 6, 2009 at 11:48 AM, Alan Livie <[email protected]> wrote: >> >> @brian, you're correct but I still don't understand. >> >> If I shorten HAS NOT to HASN'T why is shortening IT IS to IT'S wrong? >> >> English is so confusing sometimes! >> >> Alan >> >> ________________________________ >> From: Brian Kotek <[email protected]> >> To: [email protected] >> Sent: Friday, March 6, 2009 4:15:13 PM >> Subject: [transfer-dev] Re: Have a One to Many relationship while still >> being able to query by the child foreign key >> >> ITS, not IT'S. I hate when I do that! >> >> On Fri, Mar 6, 2009 at 11:14 AM, Brian Kotek <[email protected]> wrote: >>> >>> I don't believe so. You'll need to remove it and either use TQL to do >>> your list query, or write your own list query yourself outside of Transfer. >>> Part of the point of Transfer is that you're dealing with Objects and their >>> relationships, not tables and foreign keys. So trying to "go behind it's >>> back" and do things like using foreign key columns directly is discouraged. >> >> > > > > > -- Bob Silverberg www.silverwareconsulting.com --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
