comp.databases.theory

• Thread Index

---

• Re: Good way to implement string interning?
  • From: Jan Hidders
• Re: MV Keys
  • From: dawn
• Re: Good way to implement string interning?
  • From: Peter Seibel
• Re: Good way to implement string interning?
  • From: Jan Hidders
• Re: We have a troll
  • From: Mark Johnson
• Good way to implement string interning?
  • From: Peter Seibel
• Re: Declarative constraints in practical terms
  • From: x
• Re: Declarative constraints in practical terms
  • From: David Cressey
• Re: Declarative constraints in practical terms
  • From: x
• Re: Declarative constraints in practical terms
  • From: x
• Re: We have a troll
  • From: onedaywhen
• Re: Declarative constraints in practical terms
  • From: x
• Re: Declarative constraints in practical terms
  • From: David Cressey
• Re: We have a troll
  • From: Tony Rogerson
• Re: MV Keys
  • From: Jon Heggland
• Re: Declarative constraints in practical terms
  • From: x
• Re: Declarative constraints in practical terms
  • From: x
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Brian Selzer
• Re: Declarative constraints in practical terms
  • From: ralphbecket
• Re: Database Schema for delicious ( Tag Structure)
  • From: zeldorblat
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: MV Keys (was: Key attributes with list values)
  • From: dawn
• Re: MV Keys (was: Key attributes with list values)
  • From: David Cressey
• Re: Declarative constraints in practical terms
  • From: Mikito Harakiri
• Re: Declarative constraints in practical terms
  • From: ralphbecket
• Re: Question about Linear hashing: A New Tool ...
  • From: Peter Seibel
• Re: Question about Linear hashing: A New Tool ...
  • From: Mikito Harakiri
• Re: MV Keys (was: Key attributes with list values)
  • From: dawn
• Question about Linear hashing: A New Tool ...
  • From: Peter Seibel
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Brian Selzer
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Brian Selzer
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Anith Sen
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Anith Sen
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Marshall Spight
• Re: MV Keys (was: Key attributes with list values)
  • From: David Cressey
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Brian Selzer
• Re: Declarative constraints in practical terms
  • From: x
• Re: Declarative constraints in practical terms
  • From: x
• Re: Declarative constraints in practical terms
  • From: x
• Re: MV Keys (was: Key attributes with list values)
  • From: dawn
• Re: Declarative constraints in practical terms
  • From: x
• Re: Declarative constraints in practical terms
  • From: David Cressey
• Re: Declarative constraints in practical terms
  • From: David Cressey
• Re: Latest version of glossary
  • From: dawn
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Anith Sen
• Re: Declarative constraints in practical terms
  • From: x
• Re: Declarative constraints in practical terms
  • From: David Cressey
• Re: Declarative constraints in practical terms
  • From: Alfredo Novoa
• Re: Declarative constraints in practical terms
  • From: David Cressey
• Re: Declarative constraints in practical terms
  • From: x
• Re: MV Keys (was: Key attributes with list values)
  • From: David Cressey
• Re: MV Keys (was: Key attributes with list values)
  • From: David Cressey
• Re: MV Keys (was: Key attributes with list values)
  • From: David Cressey
• Re: MV Keys (was: Key attributes with list values)
  • From: David Cressey
• Re: We have a troll
  • From: Roy Hann
• Re: Latest version of glossary
  • From: x
• Re: How to work with m:n relationships?
  • From: Jonathan Leffler
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Brian Selzer
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Marshall Spight
• Re: MV Keys (was: Key attributes with list values)
  • From: Marshall Spight
• Re: Document order (was: MV Keys)
  • From: Mark Johnson
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: JOG
• Re: MV Keys (was: Key attributes with list values)
  • From: Marshall Spight
• Re: MV Keys (was: Key attributes with list values)
  • From: JOG
• Re: MV Keys (was: Key attributes with list values)
  • From: Mark Johnson
• Re: MV Keys (was: Key attributes with list values)
  • From: dawn
• Re: MV Keys (was: Key attributes with list values)
  • From: JOG
• Re: MV Keys
  • From: dawn
• Re: MV Keys (was: Key attributes with list values)
  • From: dawn
• Re: MV Keys
  • From: Marshall Spight
• Re: MV Keys (was: Key attributes with list values)
  • From: Marshall Spight
• Re: MV Keys (was: Key attributes with list values)
  • From: Marshall Spight
• Re: MV Keys
  • From: Marshall Spight
• Re: MV Keys
  • From: Marshall Spight
• Re: MV Keys (was: Key attributes with list values)
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: Marshall Spight
• Re: Declarative constraints in practical terms
  • From: Marshall Spight
• Re: How to work with m:n relationships?
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: Marshall Spight
• Re: MV Keys (was: Key attributes with list values)
  • From: Marshall Spight
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Marshall Spight
• Re: Declarative constraints in practical terms
  • From: dawn
• Document order (was: MV Keys)
  • From: mAsterdam
• Re: We have a troll
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: Marshall Spight
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Brian Selzer
• Re: Declarative constraints in practical terms
  • From: David Cressey
• Re: Declarative constraints in practical terms
  • From: Bob Hairgrove
• Re: MV Keys (was: Key attributes with list values)
  • From: Bob Hairgrove
• Re: We have a troll
  • From: -CELKO-
• Re: Declarative constraints in practical terms
  • From: Marshall Spight
• Re: Declarative constraints in practical terms
  • From: Marshall Spight
• Re: MV Keys
  • From: mAsterdam
• Re: MV Keys (was: Key attributes with list values)
  • From: Bob Hairgrove
• Re: MV Keys (was: Key attributes with list values)
  • From: David Cressey
• Re: Declarative constraints in practical terms
  • From: David Cressey
• Re: Declarative constraints in practical terms
  • From: Bob Hairgrove
• Re: Declarative constraints in practical terms
  • From: Marshall Spight
• Re: MV Keys (was: Key attributes with list values)
  • From: Bob Hairgrove
• Re: MV Keys
  • From: mAsterdam
• Re: Declarative constraints in practical terms
  • From: Bob Hairgrove
• Re: MV Keys
  • From: dawn
• Re: Declarative constraints in practical terms
  • From: Bob Hairgrove
• Re: Declarative constraints in practical terms
  • From: David Cressey
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: MV Keys (was: Key attributes with list values)
  • From: David Cressey
• Re: Declarative constraints in practical terms
  • From: Marshall Spight
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Marshall Spight
• Re: Declarative constraints in practical terms
  • From: Bob Hairgrove
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Brian Selzer
• Re: Declarative constraints in practical terms
  • From: Marshall Spight
• Re: MV Keys (was: Key attributes with list values)
  • From: Marshall Spight
• Re: MV Keys
  • From: mAsterdam
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: [OT] We have a troll
  • From: Mark Johnson
• Re: We have a troll
  • From: Mark Johnson
• Re: MV Keys (was: Key attributes with list values)
  • From: dawn
• Re: The horse race
  • From: Mark Johnson
• Re: The horse race
  • From: Tony Andrews
• Re: We have a troll
  • From: Todd
• MV Keys (was: Key attributes with list values)
  • From: mAsterdam
• Re: Declarative constraints in practical terms
  • From: Frank Hamersley
• Re: We have a troll
  • From: mAsterdam
• Re: [OT] We have a troll
  • From: Frank Hamersley
• Re: We have a troll
  • From: Mark Johnson
• Re: We have a troll
  • From: JOG
• Re: [OT] We have a troll
  • From: Mark Johnson
• Re: We have a troll
  • From: Mark Johnson
• Re: [OT] We have a troll
  • From: Mark Johnson
• Re: [OT] We have a troll
  • From: Mark Johnson
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Marshall Spight
• Re: The horse race
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: ralphbecket
• Re: Database design
  • From: Mark Johnson
• Re: Define "flatten database" ?
  • From: Mark Johnson
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Marshall Spight
• Re: cdt glossary 0.1.0
  • From: Mark Johnson
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: dawn
• Re: OT: writing style
  • From: Mark Johnson
• Re: [OT] We have a troll
  • From: Mark Johnson
• Re: [OT] We have a troll
  • From: David Cressey
• Re: We have a troll
  • From: JOG
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Brian Selzer
• Re: We have a troll
  • From: Mark Johnson
• Re: [OT] We have a troll
  • From: Christopher Browne
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Sad, but true ... (???)
  • From: Frank Hamersley
• Re: We have a troll
  • From: dawn
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: dawn
• Re: Database Schema for delicious ( Tag Structure)
  • From: Jay Dee
• Re: How to use Decode function
  • From: J M Davitt
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Marshall Spight
• Re: cdt glossary 0.1.0 [Relation]
  • From: Jay Dee
• [OT] We have a troll
  • From: Marshall Spight
• Re: Declarative constraints in practical terms
  • From: Alfredo Novoa
• Re: OT: writing style
  • From: mAsterdam
• Re: cdt glossary 0.1.0
  • From: mAsterdam
• Re: Define "flatten database" ?
  • From: David Cressey
• Re: Latest version of glossary
  • From: David Cressey
• Re: Database design
  • From: mAsterdam
• Re: The horse race
  • From: JOG
• Re: Define "flatten database" ?
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: OT: writing style
  • From: s.j.lagoe
• Re: The horse race
  • From: Mark Johnson
• Re: OT: writing style
  • From: Mark Johnson
• Re: OT: writing style
  • From: Mark Johnson
• Re: cdt glossary 0.1.0 [Data]
  • From: JOG
• Re: Database Schema for delicious ( Tag Structure)
  • From: David Portas
• Database Schema for delicious ( Tag Structure)
  • From: friend.05
• Re: Latest version of glossary
  • From: JOG
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: dawn
• Re: Latest version of glossary
  • From: dawn
• Re: Key attributes with list values was Re: What are the differences ...KEY
  • From: Bob Hairgrove
• Key attributes with list values was Re: What are the differences ...KEY
  • From: dawn
• Re: What are the differences between the terms, CANDIDATE KEY, PRIMARY KEY, SUPER KEY, COMPOSITE KEY?
  • From: Marshall Spight
• Re: Latest version of glossary
  • From: JOG
• Re: cdt glossary 0.1.0 [Data]
  • From: David Cressey
• Re: Database design
  • From: David Cressey
• Re: OT: writing style
  • From: s.j.lagoe
• Re: Sad, but true ... (???)
  • From: David Cressey
• Re: OT: writing style
  • From: mAsterdam
• Re: Latest version of glossary
  • From: David Cressey
• Re: Latest version of glossary
  • From: David Cressey
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Declarative constraints in practical terms
  • From: David Cressey
• Re: How to use Decode function
  • From: Bob Hairgrove
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Declarative constraints in practical terms
  • From: David Cressey
• Re: Database design
  • From: mAsterdam
• Re: Database design
  • From: David Cressey
• How to use Decode function
  • From: poojareddys
• Re: Define "flatten database" ?
  • From: David Cressey
• Re: cdt glossary 0.1.0 [Relation]
  • From: dawn
• Re: The horse race
  • From: Tony Andrews
• Re: Define "flatten database" ?
  • From: Jan Hidders
• Re: OT: writing style
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: Frank Hamersley
• Re: Database design
  • From: Mark Johnson
• Re: OT: writing style
  • From: mAsterdam
• Re: Database design
  • From: mAsterdam
• Re: Database design
  • From: mAsterdam
• Re: Design question regarding data typing
  • From: Bob Hairgrove
• Re: OT: writing style (was: Database design)
  • From: Mark Johnson
• cdt glossary 0.1.0 [Relation]
  • From: Mark Johnson
• OT: writing style (was: Database design)
  • From: mAsterdam
• Re: Declarative constraints in practical terms
  • From: Jan Hidders
• Re: What are the differences between the terms, CANDIDATE KEY, PRIMARY KEY, SUPER KEY, COMPOSITE KEY?
  • From: Jan Hidders
• Re: Define "flatten database" ?
  • From: Jan Hidders
• Re: Declarative constraints in practical terms
  • From: Frank Hamersley
• Re: Latest version of glossary
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Location Structures Approaches, Pros & Cons
  • From: Mark Johnson
• Re: Latest version of glossary
  • From: JOG
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Declarative constraints in practical terms
  • From: Brian Selzer
• Re: Location Structures Approaches, Pros & Cons
  • From: dawn
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Location Structures Approaches, Pros & Cons
  • From: jason.glumidge@xxxxxxxxx
• Re: Database design
  • From: s.j.lagoe
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Declarative constraints in practical terms
  • From: Frank Hamersley
• Re: Declarative constraints in practical terms
  • From: Frank Hamersley
• Re: Location Structures Approaches, Pros & Cons
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Sad, but true ... (???)
  • From: Frank Hamersley
• Re: cdt glossary 0.1.0
  • From: Mark Johnson
• Re: cdt glossary 0.1.0
  • From: dawn
• Re: cdt glossary 0.1.0 [Data]
  • From: mAsterdam
• Re: cdt glossary 0.1.0 [Data]
  • From: dawn
• OT: subject line (was: something glossary)
  • From: mAsterdam
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Database design
  • From: mAsterdam
• Re: Design question regarding data typing
  • From: Jacob JKW
• Re: cdt glossary 0.1.0 [Data]
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Sad, but true ... (???)
  • From: David Cressey
• Re: Declarative constraints in practical terms
  • From: Jon Heggland
• Re: Declarative constraints in practical terms
  • From: David Cressey
• Re: Database design
  • From: Mark Johnson
• Re: cdt glossary 0.1.0 [Data]
  • From: Marshall Spight
• Re: The horse race
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: David Cressey
• Re: The horse race
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: mAsterdam
• Re: Location Structures Approaches, Pros & Cons
  • From: Tim Marshall
• Re: Location Structures Approaches, Pros & Cons
  • From: Tim Marshall
• Re: Latest version of glossary
  • From: Marshall Spight
• Re: Design question regarding data typing
  • From: Bob Hairgrove
• Re: Design question regarding data typing
  • From: Marshall Spight
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: cdt glossary 0.1.0 [Data]
  • From: mAsterdam
• cdt glossary 0.1.0 [Data]
  • From: mAsterdam
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Latest version of glossary
  • From: mAsterdam
• Re: Latest version of glossary
  • From: mAsterdam
• Re: Latest version of glossary
  • From: mAsterdam
• Re: Latest version of glossary
  • From: mAsterdam
• cdt glossary 0.1.0
  • From: mAsterdam
• Re: Design question regarding data typing
  • From: Bob Hairgrove
• Re: How to work with m:n relationships?
  • From: David Portas
• Re: How to work with m:n relationships?
  • From: vldm10
• Re: What are the differences between the terms, CANDIDATE KEY, PRIMARY KEY, SUPER KEY, COMPOSITE KEY?
  • From: Marshall Spight
• Re: Design question regarding data typing
  • From: Jacob JKW
• Re: Design question regarding data typing
  • From: Jacob JKW
• Re: What are the differences between the terms, CANDIDATE KEY, PRIMARY KEY, SUPER KEY, COMPOSITE KEY?
  • From: Brian Selzer
• Re: What are the differences between the terms, CANDIDATE KEY, PRIMARY KEY, SUPER KEY, COMPOSITE KEY?
  • From: Mikito Harakiri
• Re: Design question regarding data typing
  • From: Marshall Spight
• Re: What are the differences between the terms, CANDIDATE KEY, PRIMARY KEY, SUPER KEY, COMPOSITE KEY?
  • From: Marshall Spight
• Re: What are the differences between the terms, CANDIDATE KEY, PRIMARY KEY, SUPER KEY, COMPOSITE KEY?
  • From: Mikito Harakiri
• Re: Design question regarding data typing
  • From: Roy Hann
• Re: What are the differences between the terms, CANDIDATE KEY, PRIMARY KEY, SUPER KEY, COMPOSITE KEY?
  • From: Mikito Harakiri
• Re: Design question regarding data typing
  • From: Bob Hairgrove
• Re: What are the differences between the terms, CANDIDATE KEY, PRIMARY KEY, SUPER KEY, COMPOSITE KEY?
  • From: Abhishek
• Re: Design question regarding data typing
  • From: Jacob JKW
• Re: Design question regarding data typing
  • From: Marshall Spight
• Re: Design question regarding data typing
  • From: Jacob JKW
• Re: Books
  • From: dawn
• Re: Database design
  • From: Gene Wirchenko
• Re: Sad, but true ... (???)
  • From: dawn
• Re: Latest version of glossary
  • From: dawn
• Re: Sad, but true ... (???)
  • From: Marshall Spight
• Re: The horse race
  • From: Marshall Spight
• WWW/Internet 2006: Call for Papers
  • From: natty2006@xxxxxxxxx
• Re: Latest version of glossary
  • From: JOG
• Re: Design question regarding data typing
  • From: Bob Hairgrove
• Sad, but true ... (???)
  • From: Bob Hairgrove
• Re: Design question regarding data typing
  • From: Jacob JKW
• Re: Design question regarding data typing
  • From: Jacob JKW
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Latest version of glossary
  • From: dawn
• Re: Latest version of glossary
  • From: x
• Re: Database design
  • From: s.j.lagoe
• Re: Latest version of glossary
  • From: michael
• Re: Latest version of glossary
  • From: x
• Re: The horse race
  • From: Tony Andrews
• Re: Declarative constraints in practical terms
  • From: Frank Hamersley
• Re: Latest version of glossary
  • From: Alexandr Savinov
• Re: Latest version of glossary
  • From: Alexandr Savinov
• Re: Design question regarding data typing
  • From: Bob Hairgrove
• Re: Latest version of glossary
  • From: x
• Re: Latest version of glossary
  • From: Alexandr Savinov
• Re: Latest version of glossary
  • From: x
• Re: Latest version of glossary
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Latest version of glossary
  • From: x
• Re: Design question regarding data typing
  • From: Roy Hann
• Re: Latest version of glossary
  • From: x
• Re: Latest version of glossary
  • From: Alexandr Savinov
• Re: Database design
  • From: x
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: x
• Books
  • From: ehabaziz2001
• Re: Database design
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: x
• Re: Database design
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: dawn
• Design question regarding data typing
  • From: Jacob JKW
• Re: Database design
  • From: Marshall Spight
• Re: Declarative constraints in practical terms
  • From: Frank Hamersley
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Marshall Spight
• Re: Declarative constraints in practical terms
  • From: Brian Selzer
• Re: Database design
  • From: JOG
• Re: Database design
  • From: Mark Johnson
• Re: Latest version of glossary
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: Brian Selzer
• Re: Declarative constraints in practical terms
  • From: Brian Selzer
• Re: Declarative constraints in practical terms
  • From: ralphbecket
• Re: Database design
  • From: JOG
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: JOG
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: The horse race
  • From: Gene Wirchenko
• Re: The horse race
  • From: Mark Johnson
• Latest version of glossary
  • From: dawn
• Re: Database design
  • From: JOG
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Frank Hamersley
• Re: The horse race
  • From: JOG
• Re: Database design
  • From: JOG
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: The horse race
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: The horse race
  • From: JOG
• Re: Database design
  • From: JOG
• Re: Database design
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: Frank Hamersley
• Re: What are the differences between the terms, CANDIDATE KEY, PRIMARY KEY, SUPER KEY, COMPOSITE KEY?
  • From: Mark Johnson
• Re: What are the differences between the terms, CANDIDATE KEY, PRIMARY KEY, SUPER KEY, COMPOSITE KEY?
  • From: Mark Johnson
• Re: Database design
  • From: mAsterdam
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Sales db design...
  • From: Me
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: The horse race
  • From: mAsterdam
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Database design
  • From: mAsterdam
• Re: Database design
  • From: mAsterdam
• Re: The horse race
  • From: Gene Wirchenko
• Re: Database design
  • From: x
• Re: Declarative constraints in practical terms
  • From: x
• Re: Database design
  • From: x
• Re: Sales db design...
  • From: Volker Hetzer
• Re: Database design
  • From: x
• Sales db design...
  • From: Me
• Re: How to work with m:n relationships?
  • From: vldm10
• Re: Database design
  • From: Alexandr Savinov
• Re: Database design
  • From: x
• Re: Database design
  • From: x
• Re: Database design
  • From: Alexandr Savinov
• Re: Database design
  • From: x
• Re: Database design
  • From: Alexandr Savinov
• Re: Database design
  • From: x
• Re: Database design
  • From: x
• Re: Database design
  • From: Alexandr Savinov
• Re: Database design
  • From: x
• Re: Database design
  • From: Marshall Spight
• Re: Database design
  • From: x
• Re: The horse race
  • From: Marshall Spight
• Re: The horse race
  • From: Marshall Spight
• Re: Database design
  • From: Marshall Spight
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: The horse race
  • From: Mark Johnson
• Re: The horse race
  • From: Mark Johnson
• Re: The horse race
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Marshall Spight
• Re: The horse race
  • From: Mark Johnson
• Re: The horse race
  • From: Marshall Spight
• Re: The horse race
  • From: Marshall Spight
• Re: The horse race
  • From: Mark Johnson
• Re: XQuery (and XML) vs LISP
  • From: Jonathan Leffler
• Re: The horse race
  • From: Marshall Spight
• Re: The horse race
  • From: Frank Hamersley
• Re: The horse race
  • From: Marshall Spight
• Re: Database design
  • From: Mark Johnson
• Re: The horse race
  • From: Mark Johnson
• Re: The horse race
  • From: Mark Johnson
• Re: Database design
  • From: Christopher Browne
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: The horse race
  • From: Marshall Spight
• Re: Database design
  • From: Frank Hamersley
• Re: XQuery (and XML) vs LISP
  • From: Frank Hamersley
• Re: Declarative constraints in practical terms
  • From: Frank Hamersley
• Re: Database design
  • From: Mark Johnson
• Re: The horse race
  • From: Marshall Spight
• Re: The horse race
  • From: Mark Johnson
• Re: The horse race
  • From: Mark Johnson
• Re: The horse race
  • From: Mark Johnson
• Re: Database or store to handle 30 Mb/sec and 40,000 inserts/sec
  • From: paul c
• Re: Declarative constraints in practical terms
  • From: ralphbecket
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Declarative constraints in practical terms
  • From: mAsterdam
• Re: Database design
  • From: mAsterdam
• Re: Database design
  • From: Marshall Spight
• Re: The horse race
  • From: Marshall Spight
• Re: The horse race
  • From: Marshall Spight
• Re: Database design
  • From: Marshall Spight
• Re: Database design
  • From: Gene Wirchenko
• Re: The horse race
  • From: Marshall Spight
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: mAsterdam
• Re: Database design
  • From: Mark Johnson
• Re: The horse race
  • From: Mark Johnson
• Re: The horse race
  • From: Mark Johnson
• Re: The horse race
  • From: Mark Johnson
• Re: The horse race
  • From: Mark Johnson
• Re: Database design
  • From: Marshall Spight
• Re: Database design
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: The horse race
  • From: Marshall Spight
• Re: Declarative constraints in practical terms
  • From: mAsterdam
• Re: The horse race
  • From: Marshall Spight
• Re: The horse race
  • From: Marshall Spight
• Re: Database design
  • From: Marshall Spight
• Re: The horse race
  • From: Bob Hairgrove
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Declarative constraints in practical terms
  • From: x
• Re: Database design
  • From: x
• Re: The horse race
  • From: x
• Re: Database design
  • From: x
• Re: Database design
  • From: Alexandr Savinov
• Re: The horse race
  • From: Volker Hetzer
• Re: Database design
  • From: x
• Re: Database design
  • From: Alexandr Savinov
• Re: Database design
  • From: x
• Re: Database design
  • From: x
• Re: Database design
  • From: Daniel Dittmar
• Re: Database design
  • From: dawn
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: Database design
  • From: x
• Re: The horse race
  • From: x
• Re: Database design
  • From: x
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Alexandr Savinov
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Alexandr Savinov
• Re: Database design
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: Brian Selzer
• Re: The horse race
  • From: Mark Johnson
• Re: XQuery (and XML) vs LISP
  • From: x
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: repeating groups
  • From: Frank Hamersley
• Re: XQuery (and XML) vs LISP
  • From: Frank Hamersley
• Re: XQuery (and XML) vs LISP
  • From: Frank Hamersley
• Re: Database design
  • From: Frank Hamersley
• Re: Database design
  • From: Christopher Browne
• Re: Database design
  • From: Marshall Spight
• Re: Database design
  • From: Marshall Spight
• Re: Database design
  • From: Marshall Spight
• Re: Database design
  • From: JOG
• Re: Declarative constraints in practical terms
  • From: Frank Hamersley
• Re: Database design
  • From: dawn
• Re: Database design
  • From: Gene Wirchenko
• Re: Database design
  • From: JOG
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: JOG
• Re: Declarative constraints in practical terms
  • From: dawn
• Re: What are the differences between the terms, CANDIDATE KEY, PRIMARY KEY, SUPER KEY, COMPOSITE KEY?
  • From: Brian Selzer
• Re: Database design
  • From: mAsterdam
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: mAsterdam
• Re: The horse race
  • From: Mark Johnson
• Re: Declarative constraints in practical terms
  • From: mAsterdam
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: mAsterdam
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Long Post - Re: How are OO databases doing
  • From: Bob Walker
• Re: XQuery (and XML) vs LISP
  • From: Marshall Spight
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: The horse race
  • From: Mark Johnson
• Re: The horse race
  • From: Mark Johnson
• Re: XQuery (and XML) vs LISP
  • From: Gene Wirchenko
• Re: XQuery (and XML) vs LISP
  • From: Marshall Spight
• Re: How to work with m:n relationships?
  • From: David Portas
• Declarative constraints in practical terms
  • From: dawn
• Re: XQuery (and XML) vs LISP
  • From: vc
• Re: What are the differences between the terms, CANDIDATE KEY, PRIMARY KEY, SUPER KEY, COMPOSITE KEY?
  • From: Anith Sen
• Re: XQuery (and XML) vs LISP
  • From: Gene Wirchenko
• Re: XQuery (and XML) vs LISP
  • From: Gene Wirchenko
• Re: repeating groups
  • From: Marshall Spight
• Re: The horse race
  • From: Bob Hairgrove
• Re: repeating groups
  • From: mAsterdam
• Re: repeating groups
  • From: dawn
• Re: The horse race
  • From: Marshall Spight
• Re: Long Post - Re: How are OO databases doing
  • From: bob
• Re: XQuery (and XML) vs LISP
  • From: Marshall Spight
• Re: repeating groups
  • From: Marshall Spight
• Re: The horse race
  • From: Volker Hetzer
• Re: The horse race
  • From: x
• Re: XQuery (and XML) vs LISP
  • From: David Cressey
• Re: The horse race
  • From: Volker Hetzer
• Re: The horse race
  • From: David Cressey
• Re: The horse race
  • From: David Cressey
• Re: repeating groups
  • From: David Cressey
• Re: XQuery (and XML) vs LISP
  • From: x
• Re: XQuery (and XML) vs LISP
  • From: x
• Re: Multilingual table design questions
  • From: x
• Re: The horse race
  • From: Daniel Dittmar
• Re: Database design
  • From: x
• Re: Database design
  • From: Frank Hamersley
• Re: Database design
  • From: x
• What are the differences between the terms, CANDIDATE KEY, PRIMARY KEY, SUPER KEY, COMPOSITE KEY?
  • From: Abhishek
• Re: Database design
  • From: Volker Hetzer
• Re: repeating groups
  • From: Frank Hamersley
• Re: XQuery (and XML) vs LISP
  • From: Frank Hamersley
• Re: XQuery (and XML) vs LISP
  • From: Frank Hamersley
• Re: XQuery (and XML) vs LISP
  • From: Frank Hamersley
• Re: Database design
  • From: Alexandr Savinov
• Re: Database design
  • From: Alexandr Savinov
• Re: Database design
  • From: Alexandr Savinov
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: The horse race
  • From: Mark Johnson
• Re: repeating groups
  • From: x
• Re: The horse race
  • From: Bob Hairgrove
• Re: repeating groups
  • From: x
• Re: Database design
  • From: x
• Re: Database design
  • From: x
• Re: Database design
  • From: x
• Re: repeating groups
  • From: Marshall Spight
• Re: Database design
  • From: x
• Re: XQuery (and XML) vs LISP
  • From: x
• Re: repeating groups
  • From: dawn
• Re: Multilingual table design questions
  • From: Marshall Spight
• Re: Multilingual table design questions
  • From: Jonathan Leffler
• Re: repeating groups
  • From: JOG
• The horse race
  • From: Mark Johnson
• Re: Location Structures Approaches, Pros & Cons
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: Mark Johnson
• Re: Database design
  • From: JOG
• Re: How to work with m:n relationships?
  • From: vldm10
• Re: Database design
  • From: Mark Johnson
• Re: repeating groups
  • From: mAsterdam
• Re: Data Redundancy
  • From: Leif B. Kristensen
• Re: repeating groups
  • From: mAsterdam
• Re: XQuery (and XML) vs LISP
  • From: Gene Wirchenko
• Re: Multilingual table design questions
  • From: Murdoc
• Re: Multilingual table design questions
  • From: Murdoc
• Re: repeating groups
  • From: dawn
• Compare Referential Integrity issues between RDBMS and ODBMS
  • From: query
• Re: Multilingual table design questions
  • From: Guy
• Re: repeating groups
  • From: JOG
• Re: Multilingual table design questions
  • From: JOG
• Re: repeating groups
  • From: Jon Heggland
• Re: Multilingual table design questions
  • From: Jon Heggland
• Re: XQuery (and XML) vs LISP
  • From: Marshall Spight
• Re: repeating groups
  • From: Marshall Spight
• Re: Location Structures Approaches, Pros & Cons
  • From: -CELKO-
• Re: Database design
  • From: Alexandr Savinov
• Re: Database design
  • From: Roy Hann
• Re: Database design
  • From: x
• Re: Database design
  • From: Roy Hann
• Re: Database design
  • From: Roy Hann
• Re: Database design
  • From: x
• Re: Database design
  • From: Volker Hetzer
• Re: Database design
  • From: Roy Hann
• Re: Simplest open source database to make lock-free
  • From: Joe Seigh
• Re: Location Structures Approaches, Pros & Cons
  • From: Tim Marshall
• Re: Database design
  • From: Alexandr Savinov
• Re: Database design
  • From: x
• Re: Database design
  • From: Roy Hann
• Re: Database design
  • From: x
• Re: Database design
  • From: x
• Re: Data Redundancy
  • From: x
• Re: XQuery (and XML) vs LISP
  • From: x
• Re: Multilingual table design questions
  • From: x
• Re: repeating groups
  • From: x
• Re: comparing remote datadases
  • From: x
• Re: comparing remote datadases
  • From: x
• Re: XQuery (and XML) vs LISP
  • From: x
• Re: repeating groups
  • From: x
• Re: repeating groups
  • From: x
• Re: repeating groups
  • From: x
• Re: repeating groups
  • From: x
• Re: Multilingual table design questions
  • From: Murdoc
• Re: 3vl 2vl and NULL
  • From: x
• Re: repeating groups
  • From: Marshall Spight
• Re: repeating groups
  • From: Jon Heggland
• Re: Simplest open source database to make lock-free
  • From: Knut Stolze
• Re: Location Structures Approaches, Pros & Cons
  • From: Marshall Spight
• Re: How to work with m:n relationships?
  • From: Jonathan Leffler
• Re: repeating groups
  • From: dawn
• Re: Multilingual table design questions
  • From: Jonathan Leffler
• Location Structures Approaches, Pros & Cons
  • From: Tim Marshall
• Re: repeating groups
  • From: JOG
• Re: Relational Lattice, what is it good for?
  • From: vc
• Re: Relational Lattice, what is it good for?
  • From: vc
• Re: Relational Lattice, what is it good for?
  • From: vc
• Re: repeating groups
  • From: Marshall Spight
• Re: repeating groups
  • From: Frank Hamersley
• Re: repeating groups
  • From: dawn
• How to work with m:n relationships?
  • From: vldm10
• Re: repeating groups
  • From: Mikito Harakiri
• Re: Relational Lattice, what is it good for?
  • From: Mikito Harakiri
• Re: Relational Lattice, what is it good for?
  • From: Mikito Harakiri
• Re: repeating groups
  • From: dawn
• Multilingual table design questions
  • From: Guy
• Re: repeating groups
  • From: David Cressey
• Re: repeating groups
  • From: mAsterdam
• Re: repeating groups
  • From: mAsterdam
• Re: repeating groups
  • From: Marshall Spight
• Re: repeating groups
  • From: dawn
• Re: repeating groups
  • From: Marshall Spight
• Re: Database design
  • From: Mark Johnson
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: repeating groups
  • From: Jonathan Leffler
• Re: XQuery (and XML) vs LISP
  • From: Frank Hamersley
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: Relational Lattice, what is it good for?
  • From: vc
• Re: Relational Lattice, what is it good for?
  • From: vc
• Re: XQuery (and XML) vs LISP
  • From: Frank Hamersley
• repeating groups (was: something with nVL and NULL)
  • From: mAsterdam
• Re: Database design
  • From: Jonathan Leffler
• Database design
  • From: friend.05
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: 3vl 2vl and NULL
  • From: David Cressey
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: Relational Lattice, what is it good for?
  • From: Mikito Harakiri
• Re: 3vl 2vl and NULL
  • From: Marshall Spight
• Re: Relational Lattice, what is it good for?
  • From: Marshall Spight
• Re: Relational Lattice, what is it good for?
  • From: Mikito Harakiri
• Re: 3vl 2vl and NULL
  • From: David Cressey
• Re: 3vl 2vl and NULL
  • From: David Cressey
• Re: XQuery (and XML) vs LISP
  • From: Frank Hamersley
• Re: XQuery (and XML) vs LISP
  • From: Frank Hamersley
• Re: XQuery (and XML) vs LISP
  • From: David Cressey
• Re: XQuery (and XML) vs LISP
  • From: Marshall Spight
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: XQuery (and XML) vs LISP
  • From: Marshall Spight
• Re: 3vl 2vl and NULL
  • From: Marshall Spight
• Re: Relational Lattice, what is it good for?
  • From: Marshall Spight
• Re: Relational Lattice, what is it good for?
  • From: Marshall Spight
• Re: Relational Lattice, what is it good for?
  • From: Mikito Harakiri
• Re: Relational Lattice, what is it good for?
  • From: vc
• Re: Relational Lattice, what is it good for?
  • From: Mikito Harakiri
• Simplest open source database to make lock-free
  • From: Joe Seigh
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: Relational Lattice, what is it good for?
  • From: Marshall Spight
• Re: 3vl 2vl and NULL
  • From: Gene Wirchenko
• Re: Relational Lattice, what is it good for?
  • From: vc
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: 3vl 2vl and NULL
  • From: Gene Wirchenko
• Re: Long Post - Re: How are OO databases doing
  • From: Arturo Hernandez
• Re: Data Redundancy
  • From: Leif B. Kristensen
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: Has anyone attended the Wilshire Meta-Data Conference
  • From: -CELKO-
• Re: Data Redundancy
  • From: -CELKO-
• Has anyone attended the Wilshire Meta-Data Conference
  • From: Arturo Hernandez
• Re: 3vl 2vl and NULL
  • From: Leif B. Kristensen
• Re: 3vl 2vl and NULL
  • From: Marshall Spight
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: Data Redundancy
  • From: David Cressey
• Re: Multi Valued Interface Models?
  • From: David Cressey
• Re: 3vl 2vl and NULL
  • From: David Cressey
• Re: 3vl 2vl and NULL
  • From: Gene Wirchenko
• Re: Data Redundancy
  • From: Marshall Spight
• Re: Data Redundancy
  • From: dawn
• Re: Reminder, blatant ad
  • From: Tedd
• Re: Data Redundancy
  • From: Marshall Spight
• Re: XQuery (and XML) vs LISP
  • From: Marshall Spight
• Re: Data Redundancy
  • From: dawn
• Re: Data Redundancy
  • From: Marshall Spight
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: XQuery (and XML) vs LISP
  • From: FrankHamersley
• Re: 3vl 2vl and NULL
  • From: David Cressey
• Re: 3vl 2vl and NULL
  • From: FrankHamersley
• Re: Relational Lattice, what is it good for?
  • From: paul c
• Re: Data Redundancy
  • From: dawn
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: 3vl 2vl and NULL
  • From: x
• Re: 3vl 2vl and NULL
  • From: x
• Re: How are OO databases doing
  • From: x
• Re: Data Redundancy
  • From: x
• Re: Relational Lattice, what is it good for?
  • From: Marshall Spight
• Re: Do I need a PK on a join table?
  • From: Knut Stolze
• Re: XQuery (and XML) vs LISP
  • From: Mark Johnson
• Re: Reminder, blatant ad
  • From: Frank Hamersley
• Re: 3vl 2vl and NULL
  • From: Marshall Spight
• Re: Data Redundancy
  • From: Marshall Spight
• Re: Data Redundancy
  • From: dawn
• Re: Reminder, blatant ad
  • From: michael
• Re: Reminder, blatant ad
  • From: michael
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: 3vl 2vl and NULL
  • From: Mikito Harakiri
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: Relational Lattice, what is it good for?
  • From: Jan Hidders
• Re: Data Redundancy
  • From: vldm10
• Re: How are OO databases doing
  • From: Jan Hidders
• Re: 3vl 2vl and NULL
  • From: Mikito Harakiri
• Re: Reminder, blatant ad
  • From: Jan Hidders
• Re: Reminder, blatant ad
  • From: Jan Hidders
• Re: Do I need a PK on a join table?
  • From: David Portas
• Long Post - Re: How are OO databases doing
  • From: bob . walker
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: 3vl 2vl and NULL
  • From: Marshall Spight
• Re: Data Redundancy
  • From: David Portas
• Re: 3vl 2vl and NULL
  • From: dawn
• Call for Papers: IAENG International Workshop on Imaging Engineering (in IMECS 2006)
  • From: imecs__2006
• Re: How are OO databases doing
  • From: Volker Hetzer
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: How are OO databases doing
  • From: Alfredo Novoa
• Re: How are OO databases doing
  • From: Alfredo Novoa
• Re: How are OO databases doing
  • From: Alexandr Savinov
• Re: How are OO databases doing
  • From: Daniel Dittmar
• Re: Data Redundancy
  • From: x
• Re: Data Redundancy
  • From: vldm10
• Re: Do I need a PK on a join table?
  • From: Knut Stolze
• Re: Reminder, blatant ad
  • From: x
• Re: 3vl 2vl and NULL
  • From: Jon Heggland
• Re: biometric data mining
  • From: Rich
• Re: Reminder, blatant ad
  • From: Frank Hamersley
• Re: OT - Best way to handle dbdebunk
  • From: JOG
• Re: Data Redundancy
  • From: paul c
• Re: Relational Lattice, what is it good for?
  • From: paul c
• Re: Data Redundancy
  • From: -CELKO-
• Re: Relational Lattice, what is it good for?
  • From: Marshall Spight
• Re: How are OO databases doing
  • From: paul c
• Re: Data Redundancy
  • From: Marshall Spight
• Re: How are OO databases doing
  • From: Marshall Spight
• Re: Reminder, blatant ad
  • From: dawn
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: filling in missing dates in a time series
  • From: paul c
• Re: Reminder, blatant ad
  • From: michael
• Re: Reminder, blatant ad
  • From: dawn
• Re: filling in missing dates in a time series
  • From: Frank Hamersley
• Re: Relational Lattice, what is it good for?
  • From: Mikito Harakiri
• Re: How are OO databases doing
  • From: paul c
• Re: 3vl 2vl and NULL
  • From: paul c
• Re: How are OO databases doing
  • From: Jan Hidders
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: How are OO databases doing
  • From: paul c
• Re: Data Redundancy
  • From: Jan Hidders
• Re: Relational Lattice, what is it good for?
  • From: paul c
• Re: How are OO databases doing
  • From: dawn
• Re: How are OO databases doing
  • From: Jan Hidders
• Re: Reminder, blatant ad
  • From: Jan Hidders
• Re: Reminder, blatant ad
  • From: dawn
• Re: How are OO databases doing
  • From: paul c
• Re: Reminder, blatant ad
  • From: paul c
• Re: How is a union different from an inheritence in ER modelling
  • From: Jan Hidders
• Re: How are OO databases doing
  • From: Jan Hidders
• Re: Reminder, blatant ad
  • From: Jan Hidders
• Re: Data Redundancy
  • From: cybose
• Re: Data Redundancy
  • From: B Faux
• Re: Relational Lattice, what is it good for?
  • From: Mikito Harakiri
• Re: Data Redundancy
  • From: paul c
• Re: filling in missing dates in a time series
  • From: paul c
• Relational Lattice, what is it good for?
  • From: Mikito Harakiri
• Data Redundancy
  • From: cybose
• Re: filling in missing dates in a time series
  • From: paul c
• Re: filling in missing dates in a time series
  • From: Bob Badour
• Re: How are OO databases doing
  • From: Bob Badour
• Re: filling in missing dates in a time series
  • From: paul c
• Re: How are OO databases doing
  • From: Alfredo Novoa
• Re: OT - Best way to handle dbdebunk
  • From: paul c
• Re: 3vl 2vl and NULL
  • From: Gene Wirchenko
• Re: How are OO databases doing
  • From: Arturo Hernandez
• Re: How are OO databases doing
  • From: Arturo Hernandez
• Re: How are OO databases doing
  • From: mAsterdam
• Re: OT - Best way to handle dbdebunk
  • From: paul c
• Re: OT - Best way to handle dbdebunk
  • From: Bob Badour
• filling in missing dates in a time series
  • From: carol_marra
• Re: How are OO databases doing
  • From: Marshall Spight
• Re: OT - Best way to handle dbdebunk
  • From: Marshall Spight
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: How are OO databases doing
  • From: Alfredo Novoa
• Re: How are OO databases doing
  • From: x
• Re: How are OO databases doing
  • From: Bob Badour
• Re: How are OO databases doing
  • From: x
• posting guidelines (was: OT - Best way to handle dbdebunk)
  • From: mAsterdam
• Re: How are OO databases doing
  • From: x
• Re: How are OO databases doing
  • From: Bob Badour
• Re: Do I need a PK on a join table?
  • From: Bob Badour
• Re: How are OO databases doing
  • From: mAsterdam
• Re: How are OO databases doing
  • From: Alfredo Novoa
• Re: Do I need a PK on a join table?
  • From: Knut Stolze
• Re: Do I need a PK on a join table?
  • From: Knut Stolze
• Re: How are OO databases doing
  • From: Daniel Dittmar
• How is a union different from an inheritence in ER modelling
  • From: Abhishek
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: Using FKs to non PK unique-indexes
  • From: vldm10
• Re: Do I need a PK on a join table?
  • From: Bob Badour
• Re: OT - Best way to handle dbdebunk
  • From: Bob Badour
• Re: OT - Best way to handle dbdebunk
  • From: Bob Badour
• Re: OT - Best way to handle dbdebunk
  • From: Alfredo Novoa
• Re: Do I need a PK on a join table?
  • From: Alfredo Novoa
• Re: Can I do this using SQL?
  • From: Volker Hetzer
• Re: OT - Best way to handle dbdebunk
  • From: Alfredo Novoa
• Re: A question in ER modelling
  • From: x
• Re: 3vl 2vl and NULL
  • From: David Cressey
• Re: Do I need a PK on a join table?
  • From: David Cressey
• Re: Can I do this using SQL?
  • From: dhruv
• Re: Can I do this using SQL?
  • From: Dieter Noeth
• Re: Can I do this using SQL?
  • From: dhruv
• Re: OT - Best way to handle dbdebunk
  • From: Roy Hann
• Re: Reminder, blatant ad
  • From: x
• Re: Multi Valued Interface Models?
  • From: x
• Re: How are OO databases doing
  • From: mAsterdam
• Re: Do I need a PK on a join table?
  • From: Knut Stolze
• Re: Multi Valued Interface Models?
  • From: x
• Re: OT - Best way to handle dbdebunk
  • From: mAsterdam
• Re: OT - Best way to handle dbdebunk
  • From: Marshall Spight
• Re: How are OO databases doing
  • From: Bob Badour
• Re: OT - Best way to handle dbdebunk
  • From: mountain man
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• How are OO databases doing
  • From: Arturo Hernandez
• Re: OT - Best way to handle dbdebunk
  • From: Bob Badour
• Re: OT - Best way to handle dbdebunk
  • From: mountain man
• Re: Oracle acquiring Sleepycat
  • From: Mikito Harakiri
• Oracle acquiring Sleepycat
  • From: dawn
• Re: Reminder, blatant ad
  • From: dawn
• Re: Reminder, blatant ad
  • From: Jan Hidders
• Re: Reminder, blatant ad
  • From: dawn
• Re: A question in ER modelling
  • From: Jan Hidders
• Re: biometric data mining
  • From: Jan Hidders
• Re: OT - Best way to handle dbdebunk
  • From: Bob Badour
• Re: OT - Best way to handle dbdebunk
  • From: dawn
• Re: Reminder, blatant ad
  • From: Jan Hidders
• A question in ER modelling
  • From: Abhishek
• A question in ER modelling
  • From: Abhishek
• Distributed MySQL Clustering/Replication
  • From: brandon
• datamining and protein
  • From: Steven Hauser
• Re: Do I need a PK on a join table?
  • From: -CELKO-
• Re: Do I need a PK on a join table?
  • From: Bob Badour
• Re: OT - Best way to handle dbdebunk
  • From: Bob Badour
• Re: OT - Best way to handle dbdebunk
  • From: Bob Badour
• Re: Do I need a PK on a join table?
  • From: Knut Stolze
• Re: Using FKs to non PK unique-indexes
  • From: paul c
• Re: Multi Valued Interface Models?
  • From: JOG
• Re: Multi Valued Interface Models?
  • From: Marshall Spight
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: Multi Valued Interface Models?
  • From: Marshall Spight
• Re: Multi Valued Interface Models?
  • From: x
• Do I need a PK on a join table?
  • From: aj
• Re: Multi Valued Interface Models?
  • From: JOG
• Re: Multi Valued Interface Models?
  • From: x
• Re: OT - Best way to handle dbdebunk
  • From: dawn
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: Multi Valued Interface Models?
  • From: x
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: Multi Valued Interface Models?
  • From: x
• Re: Multi Valued Interface Models?
  • From: x
• Re: Multi Valued Interface Models?
  • From: mAsterdam
• Re: Multi Valued Interface Models?
  • From: Marshall Spight
• Re: Multi Valued Interface Models?
  • From: x
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: OT - Best way to handle dbdebunk
  • From: Vadim Tropashko
• Re: Comments/views appreciated...
  • From: Frank Hamersley
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: Multi Valued Interface Models?
  • From: JOG
• Re: OT - Best way to handle dbdebunk
  • From: Bob Badour
• Re: OT - Best way to handle dbdebunk
  • From: mountain man
• Re: Definitions of Software and Database
  • From: mountain man
• Re: Reminder, blatant ad
  • From: dawn
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: Multi Valued Interface Models?
  • From: mAsterdam
• Re: OT - Best way to handle dbdebunk
  • From: Alfredo Novoa
• Re: Multi Valued Interface Models?
  • From: mAsterdam
• Re: OT - Best way to handle dbdebunk
  • From: Eric Junkermann
• Re: Comments/views appreciated...
  • From: B Faux
• Re: OT - Best way to handle dbdebunk
  • From: Vadim Tropashko
• Re: OT - Best way to handle dbdebunk
  • From: Roy Hann
• Re: OT - Best way to handle dbdebunk
  • From: David Fetter
• Re: Multi Valued Interface Models?
  • From: JOG
• Re: Comments/views appreciated...
  • From: Roy Hann
• Re: Multi Valued Interface Models?
  • From: x
• Re: Multi Valued Interface Models?
  • From: mAsterdam
• Re: Multi Valued Interface Models?
  • From: x
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: OT - Best way to handle dbdebunk
  • From: x
• Re: OT - Best way to handle dbdebunk
  • From: Alexandr Savinov
• Re: OT - Best way to handle dbdebunk
  • From: x
• Re: Can I do this using SQL?
  • From: Dieter Noeth
• Re: OT - Best way to handle dbdebunk
  • From: Roy Hann
• Re: OT - Best way to handle dbdebunk
  • From: x
• Re: OT - Best way to handle dbdebunk
  • From: x
• Re: 3vl 2vl and NULL
  • From: x
• Re: OT - Best way to handle dbdebunk
  • From: Alexandr Savinov
• Re: Can I do this using SQL?
  • From: Tony Rogerson
• Re: Reminder, blatant ad
  • From: x
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: Multi Valued Interface Models?
  • From: David Cressey
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: XQuery (and XML) vs LISP
  • From: Frank Hamersley
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: Can I do this using SQL?
  • From: Troels Arvin
• Re: OT - Best way to handle dbdebunk
  • From: michael
• Re: Can I do this using SQL?
  • From: Dieter Noeth
• Re: Can I do this using SQL?
  • From: Troels Arvin
• Re: Multi Valued Interface Models?
  • From: paul c
• Re: Multi Valued Interface Models?
  • From: David Cressey
• Re: OT - Best way to handle dbdebunk
  • From: Frank Hamersley
• Re: OT - Best way to handle dbdebunk
  • From: Frank Hamersley
• Re: OT - Best way to handle dbdebunk
  • From: Tony D
• Re: Database or store to handle 30 Mb/sec and 40,000 inserts/sec
  • From: Tony Rogerson
• Re: Database or store to handle 30 Mb/sec and 40,000 inserts/sec
  • From: paul c
• Re: OT - Best way to handle dbdebunk
  • From: David Fetter
• Re: OT - Best way to handle dbdebunk
  • From: -CELKO-
• Re: OT - Best way to handle dbdebunk
  • From: Todd
• biometric data mining
  • From: Rich
• OT - Best way to handle dbdebunk
  • From: dawn
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: Reminder, blatant ad
  • From: dawn
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: Reminder, blatant ad
  • From: Jan Hidders
• Re: Multi Valued Interface Models?
  • From: Jan Hidders
• Re: Reminder, blatant ad
  • From: dawn
• Re: Reminder, blatant ad
  • From: Jan Hidders
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: Query execution for intervals
  • From: Mikito Harakiri
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: transitive closure
  • From: David Fetter
• Re: XQuery (and XML) vs LISP
  • From: Mikito Harakiri
• Re: XQuery (and XML) vs LISP
  • From: beelzebub
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: Can I do this using SQL?
  • From: Dieter Noeth
• Re: Can I do this using SQL?
  • From: Dieter Noeth
• Re: Multi Valued Interface Models?
  • From: x
• Re: Multi Valued Interface Models?
  • From: x
• Re: Can I do this using SQL?
  • From: Tony Rogerson
• Re: Can I do this using SQL?
  • From: Roy Hann
• Re: Multi Valued Interface Models?
  • From: x
• Re: Can I do this using SQL?
  • From: Roy Hann
• Re: Can I do this using SQL?
  • From: Dieter Noeth
• Re: Can I do this using SQL?
  • From: Tony Rogerson
• Re: Can I do this using SQL?
  • From: Tony Rogerson
• Re: Query execution for intervals
  • From: x
• Re: Query execution for intervals
  • From: x
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: Reminder, blatant ad
  • From: paul c
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: Can I do this using SQL?
  • From: -CELKO-
• Re: Reminder, blatant ad
  • From: dawn
• Re: ER design problem
  • From: mAsterdam
• Re: Reminder, blatant ad
  • From: Leif B. Kristensen
• Re: Reminder, blatant ad
  • From: dawn
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: Reminder, blatant ad
  • From: Jan Hidders
• Re: Reminder, blatant ad
  • From: Jan Hidders
• Re: Multi Valued Interface Models?
  • From: Marshall Spight
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: ER design problem
  • From: garhone
• Re: Query execution for intervals
  • From: Mikito Harakiri
• Re: Query execution for intervals
  • From: Mikito Harakiri
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: Can I do this using SQL?
  • From: Knut Stolze
• Re: Query execution for intervals
  • From: frebe73
• Re: Multi Valued Interface Models?
  • From: JOG
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: Can I do this using SQL?
  • From: Volker Hetzer
• Re: Reminder, blatant ad
  • From: dawn
• Re: Reminder, blatant ad
  • From: x
• Re: Query execution for intervals
  • From: x
• Re: Can I do this using SQL?
  • From: dhruv
• Re: Query execution for intervals
  • From: frebe73
• Re: Can I do this using SQL?
  • From: Knut Stolze
• Re: Query execution for intervals
  • From: x
• Can I do this using SQL?
  • From: dhruv
• Re: Query execution for intervals
  • From: frebe73
• Re: Multi Valued Interface Models?
  • From: x
• Re: ER design problem
  • From: mAsterdam
• Re: Multi Valued Interface Models?
  • From: dawn
• Re: Which are the best books for data structures and algorithms for database
  • From: JOG
• Re: Reminder, blatant ad
  • From: JOG
• Re: Multi Valued Interface Models?
  • From: JOG
• Re: Reminder, blatant ad
  • From: Mikito Harakiri
• Re: Which are the best books for data structures and algorithms for database
  • From: wtxwtx@xxxxxxxxx
• Multi Valued Interface Models?
  • From: JOG
• Re: Reminder, blatant ad
  • From: Marshall Spight
• Re: Reminder, blatant ad
  • From: dawn
• Re: Which are the best books for data structures and algorithms for database
  • From: falcon
• Re: What is Weak Entity and Total participation
  • From: Jan Hidders
• Re: Reminder, blatant ad
  • From: Jan Hidders
• Re: Reminder, blatant ad
  • From: Jan Hidders
• Re: XQuery (and XML) vs LISP
  • From: Jan Hidders
• ER design problem
  • From: garhone
• What is Weak Entity and Total participation
  • From: Abhishek
• Re: Reminder, blatant ad
  • From: JOG
• request for posting guidelines
  • From: garhone
• Re: Database or store to handle 30 Mb/sec and 40,000 inserts/sec
  • From: paul c
• Re: Database or store to handle 30 Mb/sec and 40,000 inserts/sec
  • From: David Cressey
• Re: Best SQL hierarchical model for large/heavily updated graphs?
  • From: felix . lungu
• Re: Reminder, blatant ad
  • From: Marshall Spight
• OT: good spacing hint.
  • From: David Cressey
• Re: Reminder, blatant ad
  • From: David Cressey
• Re: Definitions of Software and Database
  • From: David Cressey
• Re: Definitions of Software and Database
  • From: David Cressey
• Re: XQuery (and XML) vs LISP
  • From: Marshall Spight
• Re: Reminder, blatant ad
  • From: Marshall Spight
• Re: Reminder, blatant ad
  • From: dawn
• Re: XQuery (and XML) vs LISP
  • From: dawn
• Re: Reminder, blatant ad
  • From: Jan Hidders
• Re: XQuery (and XML) vs LISP
  • From: Jan Hidders
• Re: XQuery (and XML) vs LISP
  • From: dawn
• Re: Reminder, blatant ad
  • From: dawn
• Re: Reminder, blatant ad
  • From: Jan Hidders
• Re: Reminder, blatant ad
  • From: Jan Hidders
• Re: XQuery (and XML) vs LISP
  • From: Jan Hidders
• Re: Database or store to handle 30 Mb/sec and 40,000 inserts/sec
  • From: paul c
• Re: Best SQL hierarchical model for large/heavily updated graphs?
  • From: -CELKO-
• Re: Query execution for intervals
  • From: paul c
• Re: Query execution for intervals
  • From: Frank Hamersley
• Re: Which are the best books for data structures and algorithms for database
  • From: Frank Hamersley
• Background of MDL
  • From: David Cressey
• Re: Reminder, blatant ad
  • From: David Cressey
• Re: Query execution for intervals
  • From: Tony Rogerson
• Best SQL hierarchical model for large/heavily updated graphs?
  • From: marchaos
• Re: Which are the best books for data structures and algorithms for database
  • From: wtxwtx@xxxxxxxxx
• Re: Which are the best books for data structures and algorithms for database
  • From: -CELKO-
• Re: Definitions of Software and Database
  • From: Frank Hamersley
• Re: Query execution for intervals
  • From: Frank Hamersley
• Re: Definitions of Software and Database
  • From: dawn
• Re: Definitions of Software and Database
  • From: dawn
• Re: Definitions of Software and Database
  • From: mAsterdam
• Re: Definitions of Software and Database
  • From: dawn
• Re: Definitions of Software and Database
  • From: dawn
• Re: Query execution for intervals
  • From: Mikito Harakiri
• Re: Definitions of Software and Database
  • From: Todd
• Re: Definitions of Software and Database
  • From: Todd
• Re: Reminder, blatant ad
  • From: x
• Re: Definitions of Software and Database
  • From: x
• Re: Reminder, blatant ad
  • From: JOG
• Re: Query execution for intervals
  • From: Tony Rogerson
• Re: Definitions of Software and Database
  • From: x
• Re: Definitions of Software and Database
  • From: x
• Re: Query execution for intervals
  • From: -CELKO-
• Re: Reminder, blatant ad
  • From: x
• Re: Drag an icon/object from windows desktop to Java GUI application
  • From: Christopher Browne
• Re: Reminder, blatant ad
  • From: David Cressey
• Drag an icon/object (which is an exe. and has short cut, for example java web start icon
  • From: rakesh
• Drag an icon/object from windows desktop to Java GUI application
  • From: rakesh
• Re: Reminder, blatant ad
  • From: x
• Re: Reminder, blatant ad
  • From: x
• Re: Which are the best books for data structures and algorithms for database
  • From: Troels Arvin
• Re: Reminder, blatant ad
  • From: David Cressey
• Re: Which are the best books for data structures and algorithms for database
  • From: wtxwtx@xxxxxxxxx
• Re: Query execution for intervals
  • From: frebe73
• Re: Definitions of Software and Database
  • From: Marshall Spight
• Re: Definitions of Software and Database
  • From: Marshall Spight
• Re: Definitions of Software and Database
  • From: Marshall Spight
• Re: Definitions of Software and Database
  • From: JOG
• Re: Definitions of Software and Database
  • From: dawn
• Re: Reminder, blatant ad
  • From: dawn
• Re: Definitions of Software and Database
  • From: Bob Hairgrove
• Re: Reminder, blatant ad
  • From: dawn
• Re: Definitions of Software and Database
  • From: dawn
• Re: Reminder, blatant ad
  • From: David Cressey
• Re: Query execution for intervals
  • From: Tony Rogerson
• Re: Definitions of Software and Database
  • From: Mikito Harakiri
• Re: XQuery (and XML) vs LISP
  • From: Mikito Harakiri
• Re: XQuery (and XML) vs LISP
  • From: Mikito Harakiri
• Re: Query execution for intervals
  • From: Mikito Harakiri
• Re: Query execution for intervals
  • From: frebe73
• Re: Query execution for intervals
  • From: lennart@xxxxxxxxxxxxxxxxxxx
• Re: Query execution for intervals
  • From: -CELKO-
• Re: Definitions of Software and Database
  • From: JOG
• Re: XQuery (and XML) vs LISP
  • From: Marshall Spight
• Re: Definitions of Software and Database
  • From: JOG
• Re: XQuery (and XML) vs LISP
  • From: JOG
• Re: Reminder, blatant ad
  • From: JOG
• Re: Reminder, blatant ad
  • From: Marshall Spight
• Re: Reminder, blatant ad
  • From: Marshall Spight
• Re: Reminder, blatant ad
  • From: Marshall Spight
• Re: Reminder, blatant ad
  • From: Marshall Spight
• Re: XQuery (and XML) vs LISP
  • From: Marshall Spight
• Re: Definitions of Software and Database
  • From: Marshall Spight
• Re: Definitions of Software and Database
  • From: Marshall Spight
• Which are the best books for data structures and algorithms for database
  • From: wtxwtx@xxxxxxxxx
• Re: Definitions of Software and Database
  • From: David Cressey
• Re: Definitions of Software and Database
  • From: mAsterdam
• Re: Definitions of Software and Database
  • From: mAsterdam
• Re: Definitions of Software and Database
  • From: mAsterdam
• Re: Definitions of Software and Database
  • From: mAsterdam
• Re: Definitions of Software and Database
  • From: mAsterdam
• Query execution for intervals
  • From: frebe73
• Re: Definitions of Software and Database
  • From: dawn
• Re: Definitions of Software and Database
  • From: dawn
• Re: Definitions of Software and Database
  • From: Leif B. Kristensen
• Re: Definitions of Software and Database
  • From: Bob Hairgrove
• Re: Definitions of Software and Database
  • From: dawn
• Re: Definitions of Software and Database
  • From: Bob Hairgrove
• Re: Definitions of Software and Database
  • From: Marshall Spight
• Re: Definitions of Software and Database
  • From: dawn
• Re: Definitions of Software and Database
  • From: Roy Hann
• Definitions of Software and Database
  • From: dawn
• Re: Reminder, blatant ad
  • From: x
• IADIS Database Systems 2006 Conference
  • From: natty2006@xxxxxxxxx
• Re: all foreign key should have index?
  • From: Murdoc
• Re: all foreign key should have index?
  • From: David Cressey
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: Rqst for Inventory Database Best Practices
  • From: B Faux
• Re: modeling either/or relationship...
  • From: JOG
• Re: all foreign key should have index?
  • From: Eric Junkermann
• Re: modeling either/or relationship...
  • From: -CELKO-
• Re: modeling either/or relationship...
  • From: -CELKO-
• Re: modeling either/or relationship...
  • From: -CELKO-
• Re: all foreign key should have index?
  • From: Gene Wirchenko
• Re: 3vl 2vl and NULL
  • From: Gene Wirchenko
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: all foreign key should have index?
  • From: Dan
• Re: Reminder, blatant ad
  • From: dawn
• Re: all foreign key should have index?
  • From: Murdoc
• Re: all foreign key should have index?
  • From: x
• Re: Reminder, blatant ad
  • From: x
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: Reminder, blatant ad
  • From: Bill Cooke
• Re: Reminder, blatant ad
  • From: JOG
• Re: modeling either/or relationship...
  • From: lennart@xxxxxxxxxxxxxxxxxxx
• Re: all foreign key should have index?
  • From: Gene Wirchenko
• Re: all foreign key should have index?
  • From: Tony Rogerson
• Re: modeling either/or relationship...
  • From: David Portas
• Re: all foreign key should have index?
  • From: Murdoc
• Re: modeling either/or relationship...
  • From: lennart@xxxxxxxxxxxxxxxxxxx
• Re: all foreign key should have index?
  • From: Gene Wirchenko
• Re: modeling either/or relationship...
  • From: David Portas
• Re: Reminder, blatant ad
  • From: dawn
• Re: modeling either/or relationship...
  • From: paul c
• Re: Reminder, blatant ad
  • From: x
• Re: all foreign key should have index?
  • From: lennart@xxxxxxxxxxxxxxxxxxx
• Re: Reminder, blatant ad
  • From: dawn
• Re: Reminder, blatant ad
  • From: x
• Re: Reminder, blatant ad
  • From: JOG
• Re: modeling either/or relationship...
  • From: jason.glumidge@xxxxxxxxx
• Re: modeling either/or relationship...
  • From: David Portas
• Re: modeling either/or relationship...
  • From: jason.glumidge@xxxxxxxxx
• Re: all foreign key should have index?
  • From: Tony Rogerson
• Re: Reminder, blatant ad
  • From: x
• Re: modeling either/or relationship...
  • From: David Portas
• Re: Reminder, blatant ad
  • From: x
• Re: Reminder, blatant ad
  • From: x
• Re: Reminder, blatant ad
  • From: x
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: Reminder, blatant ad
  • From: dawn
• Re: 3vl 2vl and NULL
  • From: Frank Hamersley
• Re: modeling either/or relationship...
  • From: jason.glumidge@xxxxxxxxx
• Re: 3vl 2vl and NULL
  • From: dawn
• Re: Reminder, blatant ad
  • From: dawn
• Re: all foreign key should have index?
  • From: Eric Junkermann

We are proud to have Web Hosting and Rack Housing from 9 Net Avenue Deutschland.
(18)