1. Stear me in the right database direction
Hi all,
I want to create a data base which has a handfull of tables. The main
table will have one to many links to most of the other tables but ine
link will be a many to many relationship. This database would hold text
and pictures. Preferably JPG.
What direction / system would you use. I have considered MS Access but
would like to write my own.
Any comments please
Thankyou
Tony
2. Re: Stear me in the right database direction
Tony Steward wrote:
>
> Hi all,
> I want to create a data base which has a handfull of tables. The main
> table will have one to many links to most of the other tables but ine
> link will be a many to many relationship. This database would hold text
> and pictures. Preferably JPG.
>
> What direction / system would you use. I have considered MS Access but
> would like to write my own.
>
> Any comments please
>
> Thankyou
>
> Tony
>
>
Virtually any database system out there would handle this in one way or
another, including Euphoria's database system. The key questions are
1. What is your intended application: web, desktop, single-user, multi-user?
2. How many transactions per day do you expect?
3. How many GB of data do you expect to add to the database in a year?
4. What platform will you be running the database on?
5. What platform will you be running the application on (depending on the size,
this may or may not be the same as the database)?
If you're interested in the learning experience, feel free to roll your own.
Database.e, included with Euphoria, is a great place to start. If you're
really only interested in the end result, use an existing package and
odbc or api wrappers.
HTH,
Michael Sabal
3. Re: Stear me in the right database direction
Michael J. Sabal wrote:
>
> Tony Steward wrote:
> >
> > Hi all,
> > I want to create a data base which has a handfull of tables. The main
> > table will have one to many links to most of the other tables but ine
> > link will be a many to many relationship. This database would hold text
> > and pictures. Preferably JPG.
[clip]
> >
> > Tony
> >
> >
> Virtually any database system out there would handle this in one way or
> another, including Euphoria's database system.
[clip]
Mike,
How can a JPG file be stored using the Euphoria data base system?
Ken Rhodes
100% MicroSoft Free
SuSE Linux 10.0
No AddWare, SpyWare, or Viruses!
Life is Good 
4. Re: Stear me in the right database direction
Tony Steward wrote:
>
> Hi all,
> I want to create a data base which has a handfull of tables. The main
> table will have one to many links to most of the other tables but ine
> link will be a many to many relationship. This database would hold text
> and pictures. Preferably JPG.
>
> What direction / system would you use. I have considered MS Access but
> would like to write my own.
>
> Any comments please
>
> Thankyou
>
Tony:
Just keep the JPG's in a seperate directory then all you need to
do is keep the name of the JPG in the database. If you try store
the JPG's in the database you won't save any space; in fact you
will require more space because the JPGs are already compressed;
so adding them to a database will only add to their size.
Bernie
My files in archive:
WMOTOR, XMOTOR, W32ENGIN, MIXEDLIB, EU_ENGIN, WIN32ERU, WIN32API
Can be downloaded here:
http://www.rapideuphoria.com/cgi-bin/asearch.exu?dos=on&win=on&lnx=on&gen=on&keywords=bernie+ryan
5. Re: Stear me in the right database direction
Kenneth Rhodes wrote:
> Mike,
>
> How can a JPG file be stored using the Euphoria data base system?
>
As a link or as a bitmap. Theoretically, it could also be stored as the
compressed data stream contained in the file itself. It's just a sequence
of bytes, which EDS can handle better than most (no blobs, varchar, etc. to
worry about).
