[ic] One SKU in multiple Branches of TREE
Gary Norton
interchange-users@interchange.redhat.com
Fri Jan 11 15:07:00 2002
--=_E9B4E7C7.00610EA3
Content-Type: multipart/alternative; boundary="=_E9B4E7C7.076609A4"
--=_E9B4E7C7.076609A4
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Ed,
=20
Thanks for the reply. So are you suggesting this implementation for TREE =
as well, or just in reference to Multiple Categories. It seems like a =
delimited field with multiple tree-branch paths could get quite ugly very =
quickly. However, I may not be seeing the light at the end of the tunnel =
on this either. I would think just for a normalization factor that it =
would be best in a separate table, but again I am not a DBA or Perl =
programer by trade. Just a newbie trying expand my skill set and understand=
ing.
=20
Thanks in advance,
Gary
=20
>>> edl@newmediaems.com 01/11/02 10:58AM >>>
At 07:57 PM 01/10/2002 -0700, you wrote:
>In searching the archives of the list I didn't see this addressed=20
>specifically, but I did find mention of one SKU in multiple categories.=20=
>Basically the thread mentioned creating a separate table that listed =
only=20
>sku and category (that is an abbreviated explanation of course).
>
>I am not sure if it is possible (usually it is if you are smart enough,=20=
>unfortunatly on this subject I am not) to do the same thing to support =
a=20
>single SKU in multiple branches of a tree.
>
>Example: Auto-parts store sells items that are usually selected by =
auto=20
>make and year:
>
>Shocks=3D>Ford=3D>Bronco=3D>77-79=3D>SKU
>
>However many SKU's can be used across multiple branches using the =
previous=20
>logic (ie 81-83 etc.)
>
>If this is possible, what do you think the best implementation is. I =
had=20
>thought about a 3rd table implementation as listed for the single sku =
in=20
>multiple categories thread, but wasn't sure what would need to be =
tweaked=20
>to support the TREE structure.
>
>I had a few ideas, but basically my brain-train got derailed when I =
tried=20
>to figure out how I was going to support SEARCHING and other features =
etc...
>
>FYI, I am testing this implementation on a generic install of=20
>"Construct" with the integration of the HOW TO for TREES.
>
>Thanks in advance,
>Gary
Fields like category, which are used to classify and group items, need =
not=20
contain just one value - you could theoretically make one sku a member =
of=20
as many categories as you want, by filling the category field with a =
list=20
of delimited values. This will require changes in the UI as well as in=20
front-end code, but it is quite doable - I have done so many times. =
It's=20
just not implemented in the foundation demo, AFAIK.
- Ed L.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
New Media E.M.S. Software Solutions for Business
463 Main St., Suite D eCommerce | Consulting | Hosting
Placerville, CA 95667 edl@newmediaems.com=20
(530) 622-9421 http://www.newmediaems.com=20
(866) 519-4680 Toll-Free (530) 622-9426 Fax
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
_______________________________________________
interchange-users mailing list
interchange-users@interchange.redhat.com=20
http://interchange.redhat.com/mailman/listinfo/interchange-users=20
--=_E9B4E7C7.076609A4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2712.300" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN-TOP: 2px; FONT: 8pt Tahoma; MARGIN-LEFT: 2px">
<DIV><FONT size=3D1></FONT>Ed,</DIV>
<DIV> </DIV>
<DIV>Thanks for the reply. So are you suggesting this implementation for =
TREE as=20
well, or just in reference to Multiple Categories. It seems like a =
delimited=20
field with multiple tree-branch paths could get quite ugly very quickly.=20=
However, I may not be seeing the light at the end of the tunnel on this =
either.=20
I would think just for a normalization factor that it would be best in =
a=20
separate table, but again I am not a DBA or Perl programer by trade. Just =
a=20
newbie trying expand my skill set and understanding.</DIV>
<DIV> </DIV>
<DIV>Thanks in advance,</DIV>
<DIV>Gary</DIV>
<DIV> </DIV>
<DIV><BR><BR>>>> edl@newmediaems.com 01/11/02 10:58AM=20
>>><BR>At 07:57 PM 01/10/2002 -0700, you wrote:<BR>>In =
searching the=20
archives of the list I didn't see this addressed <BR>>specifically, but =
I did=20
find mention of one SKU in multiple categories. <BR>>Basically the =
thread=20
mentioned creating a separate table that listed only <BR>>sku and =
category=20
(that is an abbreviated explanation of course).<BR>><BR>>I am not =
sure if=20
it is possible (usually it is if you are smart enough, <BR>>unfortunatly=
on=20
this subject I am not) to do the same thing to support a <BR>>single =
SKU in=20
multiple branches of a tree.<BR>><BR>>Example: Auto-parts store =
sells=20
items that are usually selected by auto <BR>>make and=20
year:<BR>><BR>>Shocks=3D>Ford=3D>Bronco=3D>77-79=3D>SKU<B=
R>><BR>>However=20
many SKU's can be used across multiple branches using the previous =
<BR>>logic=20
(ie 81-83 etc.)<BR>><BR>>If this is possible, what do you think the =
best=20
implementation is. I had <BR>>thought about a 3rd table implementation =
as=20
listed for the single sku in <BR>>multiple categories thread, but =
wasn't sure=20
what would need to be tweaked <BR>>to support the TREE=20
structure.<BR>><BR>>I had a few ideas, but basically my brain-train =
got=20
derailed when I tried <BR>>to figure out how I was going to support =
SEARCHING=20
and other features etc...<BR>><BR>>FYI, I am testing this implementat=
ion=20
on a generic install of <BR>>"Construct" with the integration of =
the=20
HOW TO for TREES.<BR>><BR>>Thanks in advance,<BR>>Gary<BR><BR>Fiel=
ds=20
like category, which are used to classify and group items, need not =
<BR>contain=20
just one value - you could theoretically make one sku a member of <BR>as =
many=20
categories as you want, by filling the category field with a list =
<BR>of=20
delimited values. This will require changes in the UI as well as =
in=20
<BR>front-end code, but it is quite doable - I have done so many times.&nbs=
p;=20
It's <BR>just not implemented in the foundation demo, AFAIK.<BR><BR>- =
Ed=20
L.<BR><BR><BR><BR><BR><BR><BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>Ne=
w=20
Media=20
E.M.S. &nb=
sp; =20
Software Solutions for Business<BR>463 Main St., Suite=20
D eCommerce | =
Consulting |=20
Hosting<BR>Placerville, CA =20
95667 =20
edl@newmediaems.com<BR>(530)=20
622-9421 &=
nbsp; =20
<A href=3D"http://www.newmediaems.com/">http://www.newmediaems.com</A><BR>(=
866)=20
519-4680 Toll-Free (530) 622-9426=20
Fax<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR><BR>___________________=
____________________________<BR>interchange-users=20
mailing list<BR>interchange-users@interchange.redhat.com<BR><A=20
href=3D"http://interchange.redhat.com/mailman/listinfo/interchange-users">h=
ttp://interchange.redhat.com/mailman/listinfo/interchange-users</A><BR></DI=
V></BODY></HTML>
--=_E9B4E7C7.076609A4--
--=_E9B4E7C7.00610EA3
Content-Type: text/plain
Content-Disposition: attachment; filename="Gary Norton.vcf"
BEGIN:VCARD
VERSION:2.1
X-GWTYPE:USER
FN:Gary Norton
EMAIL;WORK;PREF;NGW:GNORTON@broadgap.com
N:Norton;Gary
END:VCARD
--=_E9B4E7C7.00610EA3--