Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #92538 > unrolled thread
| Started by | Peter Pearson <pkpearson@nowhere.invalid> |
|---|---|
| First post | 2015-06-12 16:21 +0000 |
| Last post | 2015-06-12 16:21 +0000 |
| 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: Guidance for academic project Peter Pearson <pkpearson@nowhere.invalid> - 2015-06-12 16:21 +0000
| From | Peter Pearson <pkpearson@nowhere.invalid> |
|---|---|
| Date | 2015-06-12 16:21 +0000 |
| Subject | Re: Guidance for academic project |
| Message-ID | <cu0f7qFjkeaU1@mid.individual.net> |
On Fri, 12 Jun 2015 10:24:05 +0530, Alby Issac <issacalby@gmail.com> wrote: > > Am new to this group. [snip] Welcome. > . . . I just want to know that is it possible to implement a filter > for view updates in the database tables using python. and that filter > will help to reject false updates in the source database. To get useful advice, you might need to clarify the requirements. Does the system allow someone to update the database *without* going through the Python program? What kind of test might the Python program apply in order to recognize a false update -- for example, is falseness a matter of the data in the update, or of the authorization of the person making the update? -- To email me, substitute nowhere->runbox, invalid->com.
Back to top | Article view | comp.lang.python
csiph-web