Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #25586 > unrolled thread
| Started by | Ed Leafe <ed@leafe.com> |
|---|---|
| First post | 2012-07-18 14:13 -0500 |
| Last post | 2012-07-18 14:13 -0500 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Foxpro goto command and deleted records Ed Leafe <ed@leafe.com> - 2012-07-18 14:13 -0500
| From | Ed Leafe <ed@leafe.com> |
|---|---|
| Date | 2012-07-18 14:13 -0500 |
| Subject | Re: Foxpro goto command and deleted records |
| Message-ID | <mailman.2277.1342638823.4697.python-list@python.org> |
On Jul 18, 2012, at 12:57 PM, MRAB wrote: >> #4 is probably the most Pythonic approach. The calling code can then decide how to react to attempting to access a deleted record. Even if you're accessing data stored in VFP tables, your module should be as Pythonic as possible. >> > I disagree. I think that if you can see it should be able to go to it. The use case was a deleted record with SET DELETED ON, which means you shouldn't "see" it. -- Ed Leafe
Back to top | Article view | comp.lang.python
csiph-web