Groups | Search | Server Info | Login | Register
Groups > comp.databases.xbase.codebase > #9
| From | beboprich@gmail.com |
|---|---|
| Newsgroups | comp.databases.xbase.codebase |
| Subject | relations codebase |
| Date | 2012-07-10 09:54 -0700 |
| Organization | http://groups.google.com |
| Message-ID | <8fe99ec4-8a8b-4ef6-9657-bc68ca8bbc97@googlegroups.com> (permalink) |
We've a doubt about using relations in codebase: We have a relationship between a couple of tables, Producto and PromocionSucursal. Into Producto we have a complete serie of records (about 23,000). Into PromocionSucursal we only have part of those records (6,300 records). In Transact SQL to get all the records of table Producto and also to know which of them have a relationship with ProductoSucursal, we execute the next script: Select p.idProducto, ps.idPromocion From Producto p, PromocionSucursal ps Where p.idPRoducto *= ps.idPRoducto And ps.idSucursal = 1 If we don't use the operator *= in this script, we only get the 6,300 records we have into the table PromocionSucursal. Using the operator *= we get 23,000 records, some of them comes with null values on the field idPromocion that implies that those records has not relation. In code base we don“t know how to reply the same behavior, I mean, to use two different tables and make a join to recover all values with the same script, considering that one of the tables are not going to have all world of records that we have in the other. We appreciate any suggestions. Regards
Back to comp.databases.xbase.codebase | Previous | Next | Find similar
relations codebase beboprich@gmail.com - 2012-07-10 09:54 -0700
csiph-web