Thu Jun 29 14:49:47 PDT 2006
- Previous message: [Slony1-general] How deep an application could be affected?
- Next message: [Slony1-general] Recovering From Failover
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim C. Nasby wrote: > On Wed, Jun 28, 2006 at 08:36:01PM +0000, Christopher Browne wrote: > >> 2. SELECT * from some_table; >> >> ...now has an additional column with a pretty funky name. Potentially, >> the new column might not forcibly be "at the end", where apps might be >> prone to ignore it... >> > > Which is why SELECT * isn't good code... > It's worth observing that Slony-I didn't create the problem; it merely exposed it up front. If an application that used "SELECT *" had been pointed to a subscriber, unpredictable results would occur...
- Previous message: [Slony1-general] How deep an application could be affected?
- Next message: [Slony1-general] Recovering From Failover
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list