On Saturday, February 05, 2011 09:31:57 am Ed Leafe wrote: > On Feb 5, 2011, at 11:38 AM, Paul McNett wrote: > > I guess we'd have to check for the context. For instance: > > > > 1) sql = "select * from c where pkid=?" > > 2) sql = "select * from c where '?' in name and cat_id=?" > > > > Case 1 is straightforward; Case 2 would only interpret the second ? as a > > parameter placeholder because of being inside quotes. > > > > Sounds hairy to code for all the edge cases, but there would be > > tremendous value in having a dabo-specified parameter placeholder that > > gets converted by dabo to the backend convention at the correct time. > > If you want an unambiguous placeholder, just use something that would > not > normally appear, such as '^^' or some other unlikely combination of > symbols. Using a question mark, which already has meaning as a placeholder > as well as being a common character that might appear in text strings, is > what makes this problematic. > > > > -- Ed Leafe
I don't know but can't the "pyformat" be used or maybe the "named". Actually, I don't really see the need - DAPI 2.0 allows all sorts of ways to pass parameters - so where's the issue? Do we need one and only one paramstyle? Johnf _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
