Ah, well, you would certainly know :-)
I guess I just leaped to that conclusion, speculating that RBScript is like
VBScript (in ASP templates), that it would be the basis for templates that
could be compiled at runtime, etc.
But that was all just speculation in a vacuum, and you would know better.
Darn.
> -----Original Message-----
> > My understanding was that Swordfish... was going to use RBScript.
>
> I don't know where you got that idea. It certainly was not
> my understanding.
>
> Best,
> - Joe
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
From Fri 28 Jul 2006 13:13:28 EDT
Return-Path: <realbasic-nug-bounces at lists dot realsoftware dot com>
X-Original-To: listarchive at realsoftware dot com
Delivered-To: listarchive at realsoftware dot com
Received: by xmail.realsoftware.com (Postfix, from userid 1037)
id 2D9598CCF7F; Fri, 28 Jul 2006 10:13:55 -0700 (PDT)
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on realxserve.local
X-Spam-Level:
X-Spam-Status: No, score=-1.6 required=4.5 tests=AWL,BAYES_00,NO_REAL_NAME
autolearn=no version=3.1.1
Received: from lists.realsoftware.com (lists.realsoftware.com [209.198.132.125])
by xmail.realsoftware.com (Postfix) with ESMTP id 1963E8CCF78;
Fri, 28 Jul 2006 10:13:53 -0700 (PDT)
Received: from lists.realsoftware.com (localhost [127.0.0.1])
by lists.realsoftware.com (Postfix) with ESMTP
id 46EE213D661C; Fri, 28 Jul 2006 12:13:38 -0500 (CDT)
X-Original-To: realbasic-nug at lists dot realsoftware dot com
Delivered-To: realbasic-nug at lists dot realsoftware dot com
Received: from imo-m26.mx.aol.com (imo-m26.mx.aol.com [64.12.137.7])
by lists.realsoftware.com (Postfix) with ESMTP id 28E8A13D660D
for <realbasic-nug at lists dot realsoftware dot com>;
Fri, 28 Jul 2006 12:13:32 -0500 (CDT)
Received: from GAmoore at aol dot com
by imo-m26.mx.aol.com (mail_out_v38_r7.6.) id w.263.372efb80 (32915)
for <realbasic-nug at lists dot realsoftware dot com>;
Fri, 28 Jul 2006 13:13:29 -0400 (EDT)
From: GAmoore at aol dot com
Message-ID: <263 dot 372efb80 dot 31fb9fb8 at aol dot com>
Date: Fri, 28 Jul 2006 13:13:28 EDT
To: realbasic-nug at lists dot realsoftware dot com
MIME-Version: 1.0
X-Mailer: Thunderbird - Mac OS X sub 293
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.2
Subject: Re: server database design
X-BeenThere: realbasic-nug at lists dot realsoftware dot com
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Sender: realbasic-nug-bounces at lists dot realsoftware dot com
Errors-To: realbasic-nug-bounces at lists dot realsoftware dot com
> > What would be the file/table architecture for this situation?=A0
> > Suppose you
> > have a company that puts out a spring catalog, a fall catalog, a=A0
> > summer catalog
> > and winter catalog=A0=A0 - made up of the same items and going to the sa=
me
> > customers.
> >
> > If you had this on a server, would you have one big database with=A0
> > an items
> > table and customers table, then have a table for winter 2005,=A0
> > spring 2005, ....
> > winter 2009, etc? Or would you have the base info in one file=A0
> > (items and
> > customers) then have a separate file for each catalog?
>=20
> That really depends on what would be needed.
> Would you need to know pages, etc that each item is on ?
>=20
> Since the basic items are the same (or similar) the catalog is=A0
> basically a cross reference between the catalog issue its in, and the=A0
> items that are actually in it.
>=20
> You might make the table that is
>=20
> =A0 =A0 CATALOG
> =A0 =A0 =A0 =A0 catalog_name (spring 2005, summer 2005, fall 2005, winter=20=
2005, etc)
> =A0 =A0 =A0 =A0 catalog_id (1,2,3,4)
>=20
> Then a table that is the cross reference between catalog and products
>=20
> =A0 =A0 CATALOG_ITEMS
> =A0 =A0 =A0 =A0 catalog_id
> =A0 =A0 =A0 =A0 product_id
>=20
> This set up allows you to rename a catalog without actually doing=A0
> anything other than changing the name.
> Duplicating a catalog is
> =A0 =A0 make a new entry in the CATALOGS table (this gets a new name and I=
D)
>=20
> =A0 =A0 insert into CATALOG_ITEMS ( new id from previous step, product_id=20=
)=A0
> select product_id from CATALOG_ITEMS where catalog_id =3D catalog you=A0
> want to copy
>=20
> Now this may be simplistic as it does not hold things like page=A0
> layout information which may be important.
>=20
Thanks Norman. Actually this whole scenario is vastly simplified for the sak=
e=20
of discussion. Essentially, they would want to keep each catalog for each=20
season, then create new ones for the following year using the past year's fi=
le as=20
a template. Over time there might be a dozen or more catalogs which would=20
need to be kept separate but usually they would only be working on one at a=20=
time.=20
I am thinking to just duplicate the customer and item info in each file and=20
have each file self-contained - but it seems more efficient to have differen=
t=20
tables in a big database in some way.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|