On Tue, Jun 27, 2000 at 03:47:41PM -0700, Daniel L. Rall wrote: > I understand that, and am saying that it's yucky when every adapter must > stub out a method that is a workaround for or applies to only one > database. They don't have to - DB is an abstract class not an interface now, so DB can implement the "normal" behaviour, and the adaptor for the database that needs the workaround can implement the "weird" behaviour. No other adaptor class needs to be affected. -- Sean Legassick [EMAIL PROTECTED] ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
- Re: [PATCH] Postgresql (long) John McNally
- Transactions (was Re: [PATCH] Postgresql (long)) Nissim
- RE: Transactions (was Re: [PATCH] Postgresql (l... Christian Nichols
- Re: Transactions (was Re: [PATCH] Postgresql (l... Daniel L. Rall
- Re: Transactions John McNally
- Re: [PATCH] Postgresql (long) Jon Stevens
- Re: [PATCH] Postgresql (long) Sean Legassick
- Re: [PATCH] Postgresql (long) Daniel L. Rall
- Re: [PATCH] Postgresql (long) Sean Legassick
- Re: [PATCH] Postgresql (long) Daniel L. Rall
- Re: DB Sean Legassick
- Re: DB Daniel L. Rall
- Re: DB Sean Legassick
- Re: DB (Postgres & Transac... Nissim
- adding html related stuff to a... John McNally
- Re: adding html related stuff ... Sean Legassick
- Re: DB (Postgres & Transac... Sean Legassick
- Re: DB (Postgres & Transac... Nissim
- Re: DB (Postgres & Transac... Sean Legassick
- Re: DB (Postgres & Transac... Nissim
- Re: DB (Postgres & Transac... Sean Legassick