I/O Reader

Comments By: Lewis

• I like the idea, but I think it's just over-complicating things. You're making code rely on this specific PQL solution, when in reality you should teach them to prefix their database fields (which is simpler and doesn't require a specific solution). I think a warning of a fieldname clash would suffice.
  
  Although, I do like the idea of separating a row in to arrays of tables (as an added extra). I think I might 'borrow' that idea.
  posted on Aug 21, 2008 at 2:31pm | context
• Thanks for the link, the reset may be just what I was looking for :)
  posted on Dec 17, 2006 at 2:13pm | context
• I'm sure the K4BB I saw was much better than that, why not upload that one?
  posted on Dec 16, 2006 at 2:14pm | context
• Apart from the ability to stack them, I can't see much advantage using these. All the extra classes can make your code messy too.
  posted on Aug 28, 2006 at 11:22pm | context
• I've not gone through it completely, but your code seems incomplete and doesn't seem to work. You've missed out a lot of key functions (well they're there, just empty). Some good explanations though. You should go in to more about what they're used for and why you should use them.
  posted on Aug 28, 2006 at 11:21pm | context

• ©
• 2006
• 2007
• 2008
• 2009
• 2010
• 2011
• Peter Goodman, all rights reserved.