RE: [ErrorSystem-devel] RE: About Errorsystem DB structure

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Sorry McTails for not responding your mails faster. I would like to make
better and longer answers, but things doesn't goes very well here with th=
is
fucking upgrade.
I join the few code lines I have already do, it isn't very much and out o=
f
date, but, by now, I have no time to do more. I hope I could do more soon.
i agree with the idea of of the systemid, and have a chat, but I can't te=
ll
you when.
I'll be on holliday since from next friday to the 5 january, and i'm stil=
l
waiting for a new modem (because of my recent removal) and I don't know f=
or
the moment if I will be able to connect during this period. If I could, I
should code something, test cvs, and all. And chat with you.

Have fun,

Stephane
> -----Message d'origine-----
> De : err...@li...
> [mailto:err...@li...]De la part de
> son...@ss...
> Envoy=E9 : mardi 16 d=E9cembre 2003 22:18
> =C0 : bro...@fr...
> Cc : nw; ES-devel
> Objet : Re: [ErrorSystem-devel] RE: About Errorsystem DB structure
>
>
> Question: Am I the only developer on the list that speaks only English
> :-P. Anyway, my MySQL daemon went boom and I haven't got around to fixi=
ng
> it. I'll get it up later this week. However, I think that we don't need
> one table for everysystem. We could have one single table for all the
> error messages, and have an id field in it that shows what system, so a
> simple WHERE sysid =3D 3 would work fine. As the the DBA class, I shoul=
d
> hopefully also get that finished by weeks end. Stephane, could you plea=
se
> mail me what code you have (as I remember in an earlier email that you
> methoned you had some done). Out of curiousity, can I some idea who her=
e
> knows how to use CVS, as once we really getting coding, it's going to g=
et
> messy having 3 different people writing the same chunk of code. What we
> need is a time where everyone could chat, possiably over IRC or AIM, so=
 we
> can talk through everything. My school is getting out this Thursday, so
> hopefully, we could set a date adn time that everyone could agree to.
>
> > Hi,
> >
> > about item 1: I think so
> > about item 2: you may be right. I'm not expert with db.
> >
> > Have fun,
> >
> > Stephane
> >
> >
> >> -----Message d'origine-----
> >> De : nw [mailto:bi...@ra...]
> >> Envoy=E9 : mardi 16 d=E9cembre 2003 08:59
> >> =C0 : bro...@fr...
> >> Objet : About Errorsystem DB structure
> >>
> >>
> >> Hello.
> >> 1_) I think you are right about using system name as primary key
> >> because errorsystem server administrator must build GET-Method query
> >> and there he has to indicate primary key of system (like
> >> "errordisplay?SYSTEM=3DYOURSYSTEM&errnum=3D25&lg=3Den"). SYSTEM=3DYO=
URSYSTEM
> >> is the better way than by example SYSTEM=3D21 (if systemID field val=
ue
> >> will be 21). Name is more understandable than char id.
> >> 2_) You suggest to create one table per one system and one table per
> >> one yoursystem-language (if i understood your idea right). But if
> >> errorsystem server will manage many systems and every these systems
> >> will have many languages - wouldn't it be too slow errorsystem? Or
> >> vice versa?
> >> 3_) About "poor english" never mind. This language is not native for
> >> me too.
> >>
> >> Best Regards.
> >> nw
> >>
> >> On Mon, 15 Dec 2003 21:37:27 +0100
> >>   "BrokenClock" <bro...@fr...> wrote:
> >> >ES-Main :
> >> >"One record for one system." I never thought that ES should manage
> >> >only one
> >> >system. I thought using name as primary key. But if you tell that's
> >> >better
> >> >to have a system id as key, why not?
> >> >
> >> >About langages : I have suggest that ES would create one table for
> >> >each
> >> >langage and system. I never suggested that ES would manage only two
> >> >langage
> >> >per system. Well, but I made a mistake in the design page : the def=
lg
> >> >field
> >> >describ in the ES-main table should be used also in the
> >> >yoursystem-ini
> >> >table. It would define the default langage used by yoursystem in th=
e
> >> >yoursystem-ini table, and the default langage used by ES and all th=
e
> >> >systems
> >> >(but ones defined in the yoursystem-ini table) in the ES-main. And
> >> >default
> >> >langages did not mean that ES woould not be able to display others.
> >> >You
> >> >should add as many langages as you need. That why I thought to use
> >> >one table
> >> >per langage. So you whould have yoursystem-en table for english,
> >> >yoursystem-fr for french, and so on. Maybe I wasn'd as clear as I
> >> >wish
> >> >(pardon my poor english, I'm not very used to it, and I'm a little
> >> >tired
> >> >those days (just have a removal, big update is running just *now*,
> >> >some
> >> >difficulties with critical process, well, well, well stop complain!=
))
> >> >I mean, I don't know if a langage table is required.
> >> >About Errorlevel table : do we really need it? What the others thin=
k?
> >> >A
> >> >description in the documentation should enough?
> >> >About foreign key : see McTail mail.
> >> >
> >> >Well, it's time to go to bed, I think.
> >> >
> >> >Have fun dreams, guys
> >> >
> >> >Stephane
> >> >
> >> >
> >> >> -----Message d'origine-----
> >> >> De : nw [mailto:bi...@ra...]
> >> >> Envoy=E9 : lundi 15 d=E9cembre 2003 10:00
> >> >> =C0 : bro...@fr...
> >> >> Objet : Re: PHP developpers for ErrorSystem
> >> >>
> >> >>
> >> >> Hello.
> >> >> I've visited design page. Following is an example MySql database
> >> >> structure as i see it:
> >> >>
> >> >> ES-Main table
> >> >> _____________
> >> >> System ID (i think that errorsystem server should can manage not
> >> >>only
> >> >> one system. This field can be unique key for every system)
> >> >> System Name (that you have described)
> >> >> AdminMail (that you have described)
> >> >> DefLg (that you have described)
> >> >>
> >> >> ES-Languages table (good error system should support more than 2
> >> >> languages, let the user manage any number of languages. This tabl=
e
> >> >> only define system languages but not errors text)
> >> >> __________________
> >> >> SystemID (foreign key to associate with specific system from
> >> >>ES-Main)
> >> >> LanguageShortName (fr, eng, ru or another - used as primary key)
> >> >> LanguageFullName (France, English, Russian or another. This field
> >> >> maybe must contain native name of language - Deutsch, =D0=F3=F1=F1=
=EA=E8=E9,
> >> >>English
> >> >> or another)
> >> >>
> >> >> ES-Errors table (contain special info about errors)
> >> >> ________________
> >> >> ErrorNum (used as index and primary key)
> >> >> ErrorLevel (foreign key to asscociate with following ES-ErrorLeve=
ls
> >> >> table)
> >> >> InternalCode
> >> >> (In this table i have some doubts about errorName to use by speci=
al
> >> >> action and SpecialMsg to use by special action)
> >> >>
> >> >>
> >> >> ES-ErrorLevels table
> >> >> ____________________
> >> >> ErrorLevel (number of level, used as primary key)
> >> >> ErrorLevelDescription (like "stop the execution of the software")
> >> >>
> >> >>
> >> >> ES-Messages table (contain messages table for every language,
> >> >>defined
> >> >> in ES-Languages table)
> >> >> _________________
> >> >> LanguageShortName (used to make relation with language from
> >> >> ES-Languages table)
> >> >> ErrorNum (used foreign key to make relation with ES-Errors table)
> >> >> ErrorName (in this language)
> >> >> ShortDesc
> >> >> LongDesc
> >> >> HTMLDesc
> >> >> XMLDesc
> >> >>
> >> >> This way structured database is able to manage any numbers of err=
or
> >> >> systems in one database (became error system server), is able to =
use
> >> >> any numbers of user defined languages.
> >> >>
> >> >> I think so.
> >> >> Best Regards.
> >> >> nw.
> >> >>
> >> >> On Thu, 11 Dec 2003 16:35:01 +0100
> >> >>   "BrokenClock" <bro...@fr...> wrote:
> >> >> >Hi,
> >> >> >
> >> >> >I've already add you as a developer.
> >> >> >I was just working on an update of the design page when i receiv=
ed
> >> >> >your
> >> >> >mail. What will I say on this page in about one hour? That, as
> >> >> >McTails
> >> >> >suggested, we better planed to use SQLite (www.sqlite.com) inste=
ad
> >> >>of
> >> >> >flat
> >> >> >files. SQLite will be implemented in PHP5, which should be
> >> >>published
> >> >> >very
> >> >> >soon. Waiting, we will use MySQL. I think we should not have a l=
ot
> >> >>of
> >> >> >work
> >> >> >to add the code for SQLite, using SQL requests.
> >> >> >Check the page when it is up to date, and we will re-talk about =
it.
> >> >> >
> >> >> >Regards,
> >> >> >
> >> >> >Stephane
> >> >> >
> >>
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: IBM Linux Tutorials.
> > Become an expert in LINUX or just sharpen your skills.  Sign up
> for IBM's
> > Free Linux Tutorials.  Learn everything from the bash shell to
> sys admin.
> > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=BFick
> > _______________________________________________
> > ErrorSystem-devel mailing list
> > Err...@li...
> > https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
> >
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM=
's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admi=
n.
> Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
> _______________________________________________
> ErrorSystem-devel mailing list
> Err...@li...
> https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
>