errorsystem-devel Mailing List for ErrorSystem
Status: Planning
Brought to you by:
sonicmctails
Menu
▾
▴
errorsystem-devel — Developpers of ErrorSystem mailing list.
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(30) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <ben...@id...> - 2004-05-25 09:19:07
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
|
From: BrokenClock <bro...@fr...> - 2004-01-15 08:01:50
|
Hi all, Just done now! McTails is now admin of the project, just as I am. Have fun, Stepane > -----Message d'origine----- > De : BrokenClock [mailto:bro...@fr...] > Envoy=E9 : jeudi 15 janvier 2004 08:53 > =C0 : son...@ss...; bro...@fr... > Cc : ES-devel > Objet : RE: [ErrorSystem-devel] Happy New Year > > > Hi McTails, > > It's good to ear you again! > In a few words : > *I'll add you as admin of the project in a few minutes, > *where can I learn more about PEAR? > *I have to read again the mailing-list archives to remember what were o= ur > conclusions about the design to go on... > > Have fun, > > Stephane > > > -----Message d'origine----- > > De : err...@li... > > [mailto:err...@li...]De la part de > > son...@ss... > > Envoy=E9 : mercredi 14 janvier 2004 16:12 > > =C0 : bro...@fr... > > Cc : ES-devel > > Objet : Re: [ErrorSystem-devel] Happy New Year > > > > > > Yes, I am alive, just been real busy recently. I'll get the DB layor = in > > CVS ASAP. I don't think it's such a hot idea to make the DB layer a > > seperate section, as PHP already has it own (called PEAR, but it's no= t > > including on all PHP installs/hosts), so this should just be part of > > ErrorSystem itself. I'd be happy to co-admin, and it shouldn't be ver= y > > hard to make a working version, although getting the actual interface= s > > working will be tricky, we could have errorsystem returning > errors pretty > > easily (I could make entrys by hand in MySQL). > > SMT > > > > > Hello everybody, > > > > > > This mail to wish you an happy new year. I hope the world will > > be a better > > > place. I wish we will all have a lot of fun!: > > > > > > Regarding ES, things became a *little* messy last month. It's > > worring for > > > ES, because it's just the first mounth. I was tired, have a > lot of work, > > > you > > > know, so I wasn't a very good admin for us (maybe I'm not a > > good amdin at > > > all!). > > > Well, my suggestion now are : > > > * concentrate on our first goal : make a working version of ES, > > > * promote SonicMCTails as co-admin of the project > > > * following the last suggestion of MCTails concerning the db > management > > > (MCTails, have you already the code? , could you post and > > update the CVS?) > > > > > > To get a working version of ES, we will suppose that we are > using MySQL > > > (only MySQL, for the moment). > > > > > > Tell me quikly what you think. > > > > > > And again have fun guys, > > > > > > Stephane > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.net email is sponsored by: Perforce Software. > > > Perforce is the Fast Software Configuration Management System offer= ing > > > advanced branching capabilities and atomic changes on 50+ platforms. > > > Free Eval! http://www.perforce.com/perforce/loadprog.html > > > _______________________________________________ > > > ErrorSystem-devel mailing list > > > Err...@li... > > > https://lists.sourceforge.net/lists/listinfo/errorsystem-devel > > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Perforce Software. > > Perforce is the Fast Software Configuration Management System offerin= g > > advanced branching capabilities and atomic changes on 50+ platforms. > > Free Eval! http://www.perforce.com/perforce/loadprog.html > > _______________________________________________ > > ErrorSystem-devel mailing list > > Err...@li... > > https://lists.sourceforge.net/lists/listinfo/errorsystem-devel > > > > |
|
From: BrokenClock <bro...@fr...> - 2004-01-15 07:53:28
|
Hi McTails, It's good to ear you again! In a few words : *I'll add you as admin of the project in a few minutes, *where can I learn more about PEAR? *I have to read again the mailing-list archives to remember what were our conclusions about the design to go on... Have fun, Stephane > -----Message d'origine----- > De : err...@li... > [mailto:err...@li...]De la part de > son...@ss... > Envoy=E9 : mercredi 14 janvier 2004 16:12 > =C0 : bro...@fr... > Cc : ES-devel > Objet : Re: [ErrorSystem-devel] Happy New Year > > > Yes, I am alive, just been real busy recently. I'll get the DB layor in > CVS ASAP. I don't think it's such a hot idea to make the DB layer a > seperate section, as PHP already has it own (called PEAR, but it's not > including on all PHP installs/hosts), so this should just be part of > ErrorSystem itself. I'd be happy to co-admin, and it shouldn't be very > hard to make a working version, although getting the actual interfaces > working will be tricky, we could have errorsystem returning errors pret= ty > easily (I could make entrys by hand in MySQL). > SMT > > > Hello everybody, > > > > This mail to wish you an happy new year. I hope the world will > be a better > > place. I wish we will all have a lot of fun!: > > > > Regarding ES, things became a *little* messy last month. It's > worring for > > ES, because it's just the first mounth. I was tired, have a lot of wo= rk, > > you > > know, so I wasn't a very good admin for us (maybe I'm not a > good amdin at > > all!). > > Well, my suggestion now are : > > * concentrate on our first goal : make a working version of ES, > > * promote SonicMCTails as co-admin of the project > > * following the last suggestion of MCTails concerning the db manageme= nt > > (MCTails, have you already the code? , could you post and > update the CVS?) > > > > To get a working version of ES, we will suppose that we are using MyS= QL > > (only MySQL, for the moment). > > > > Tell me quikly what you think. > > > > And again have fun guys, > > > > Stephane > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Perforce Software. > > Perforce is the Fast Software Configuration Management System offerin= g > > advanced branching capabilities and atomic changes on 50+ platforms. > > Free Eval! http://www.perforce.com/perforce/loadprog.html > > _______________________________________________ > > ErrorSystem-devel mailing list > > Err...@li... > > https://lists.sourceforge.net/lists/listinfo/errorsystem-devel > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Perforce Software. > Perforce is the Fast Software Configuration Management System offering > advanced branching capabilities and atomic changes on 50+ platforms. > Free Eval! http://www.perforce.com/perforce/loadprog.html > _______________________________________________ > ErrorSystem-devel mailing list > Err...@li... > https://lists.sourceforge.net/lists/listinfo/errorsystem-devel > |
|
From: <son...@ss...> - 2004-01-14 15:12:16
|
Yes, I am alive, just been real busy recently. I'll get the DB layor in CVS ASAP. I don't think it's such a hot idea to make the DB layer a seperate section, as PHP already has it own (called PEAR, but it's not including on all PHP installs/hosts), so this should just be part of ErrorSystem itself. I'd be happy to co-admin, and it shouldn't be very hard to make a working version, although getting the actual interfaces working will be tricky, we could have errorsystem returning errors pretty easily (I could make entrys by hand in MySQL). SMT > Hello everybody, > > This mail to wish you an happy new year. I hope the world will be a better > place. I wish we will all have a lot of fun!: > > Regarding ES, things became a *little* messy last month. It's worring for > ES, because it's just the first mounth. I was tired, have a lot of work, > you > know, so I wasn't a very good admin for us (maybe I'm not a good amdin at > all!). > Well, my suggestion now are : > * concentrate on our first goal : make a working version of ES, > * promote SonicMCTails as co-admin of the project > * following the last suggestion of MCTails concerning the db management > (MCTails, have you already the code? , could you post and update the CVS?) > > To get a working version of ES, we will suppose that we are using MySQL > (only MySQL, for the moment). > > Tell me quikly what you think. > > And again have fun guys, > > Stephane > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Perforce Software. > Perforce is the Fast Software Configuration Management System offering > advanced branching capabilities and atomic changes on 50+ platforms. > Free Eval! http://www.perforce.com/perforce/loadprog.html > _______________________________________________ > ErrorSystem-devel mailing list > Err...@li... > https://lists.sourceforge.net/lists/listinfo/errorsystem-devel > |
|
From: BrokenClock <bro...@fr...> - 2004-01-13 08:51:27
|
Hello everybody, This mail to wish you an happy new year. I hope the world will be a better place. I wish we will all have a lot of fun!: Regarding ES, things became a *little* messy last month. It's worring for ES, because it's just the first mounth. I was tired, have a lot of work, you know, so I wasn't a very good admin for us (maybe I'm not a good amdin at all!). Well, my suggestion now are : * concentrate on our first goal : make a working version of ES, * promote SonicMCTails as co-admin of the project * following the last suggestion of MCTails concerning the db management (MCTails, have you already the code? , could you post and update the CVS?) To get a working version of ES, we will suppose that we are using MySQL (only MySQL, for the moment). Tell me quikly what you think. And again have fun guys, Stephane |
|
From: <son...@ss...> - 2003-12-25 22:58:41
|
I've got a better idea which makes it also alot easier for anyone to make
a new layer. We have the configuration variable in the file be what file
is loaded. So if $['CONFIG'] = mysql, then database-mysql.php will be
loaded. If that was changed to postgresql then database-postgresql.php.
Then all that would have to be done is set the include line to load the
right file. I've seen this system used liek that with great success on
Invision Power Board, and PHPBB (though I haven't dug into it's code to
make sure).
> In fact, the constructor, I would have prefer something like this:
> Class DBL{
> function DBL($user, $pass, $name, $server="localhost", $port=3306,
> $type="MySQL") {
> $this->user=$user;
> $this->pass=$pass;
> $this->name=$name;
> $this->server=$server;
> $this->port=$port;
> $this->type=$type;
> switch ($type) {
> case "MySQL":
> include("mysql.inc.php");
> break;
> case "ProgresSQL":
> include("progress.inc.php");
> break;
> //and so on
> }
> }
> }
> Should this work? What do you think about that?
>
> 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_id=3371&op=click
> _______________________________________________
> ErrorSystem-devel mailing list
> Err...@li...
> https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
>
|
|
From: BrokenClock <bro...@fr...> - 2003-12-22 14:45:20
|
In fact, the constructor, I would have prefer something like this:
Class DBL{
function DBL($user, $pass, $name, $server="localhost", $port=3306,
$type="MySQL") {
$this->user=$user;
$this->pass=$pass;
$this->name=$name;
$this->server=$server;
$this->port=$port;
$this->type=$type;
switch ($type) {
case "MySQL":
include("mysql.inc.php");
break;
case "ProgresSQL":
include("progress.inc.php");
break;
//and so on
}
}
}
Should this work? What do you think about that?
Stephane
|
|
From: BrokenClock <bro...@fr...> - 2003-12-22 14:25:26
|
I would have prefered to remove the include(mysql_class.php) in the
constructor, and use the parameters of the constructor for the settings
instead of a file, but it works, after all, no?
Could you please upload your work on CVS?
> -----Message d'origine-----
> De : err...@li...
> [mailto:err...@li...]De la part de
> son...@ss...
> Envoy=E9 : dimanche 21 d=E9cembre 2003 07:15
> =C0 : nw
> Cc : err...@li...
> Objet : Re: [ErrorSystem-devel] Re: ErrorSystem-devel digest, Vol 1 #9 =
-
> 4 msgs
>
>
> I have my DB Class finished, but my laptop is currently not with me (I'=
m
> with my cousins, and my laptop is home) I will get the files uploaded
> ASAP. I have two versions, one using Mysql_ and one using mysqli_ as
> mysql_ only works with version below 4.1.
>
> > Maybe we can reach compatibility with different databases by using OO=
P
> > STEP 1) Write classess for every needed database (for example -
> > mysql_class.php, mssql_class.php, anydatabase_class.php...). Methods
> > (functions) in these classes we have to name equal (for example,
> > method db_connect() must be in every class). In these classes we may
> > write methods:
> > a) db_connect() - method to connect and login db, select database
> > b) db_make_recordset() - method to execute an sql query.
> > c) db_close() - to close connection
> > Actually we have to set $dataset class variable which will store our
> > result of sql query (its like '$dataset =3D mysql_query("select * fro=
m
> > tbl")'). This variable we have to set in db_make_recordset() method.
> >
> > STEP 2) Use classes.
> > We only write code:
> > for mysql -
> > include(mysql_class.php);
> > $page =3D new page();
> > $page->db_connect(host,user,password);
> > $page->db_make_recordset(sqlquery);
> > while ($row =3D mysql_fetch_array($page->dataset, MYSQL_ASSOC)) =
{
> > printf ("ID: %s Name: %s", $row["id"], $row["name"]);
> > }
> > $page->close();
> > for anydatabase -
> > include(ANYDATABASE_class.php); // WE HAVE TO CHANGE ONLY THIS
> > $page =3D new page_class();
> > $page->db_connect(host,user,password);
> > $page->db_make_recordset(sqlquery);
> > while ($row =3D mysql_fetch_array($page->dataset, MYSQL_ASSOC)) =
{
> > printf ("ID: %s Name: %s", $row["id"], $row["name"]);
> > }
> > $page->close();
> >
> > That's all of my proposition.
> > Best Regards. nw.
> >
> >
> > On Thu, 18 Dec 2003 20:07:20 -0800
> > err...@li... wrote:
> >>Send ErrorSystem-devel mailing list submissions to
> >> err...@li...
> >>
> >>To subscribe or unsubscribe via the World Wide Web, visit
> >> https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
> >>or, via email, send a message with subject or body 'help' to
> >> err...@li...
> >>
> >>You can reach the person managing the list at
> >> err...@li...
> >>
> >>When replying, please edit your Subject line so it is more specific
> >>than "Re: Contents of ErrorSystem-devel digest..."
> >>
> >>
> >>Today's Topics:
> >>
> >> 1. RE: RE: ErrorSystem - proposal (BrokenClock)
> >> 2. Re: RE: RE: ErrorSystem - proposal (son...@ss...)
> >> 3. RE: TR: RE: [ErrorSystem-devel] home page little update
> >>(BrokenClock)
> >> 4. RE: TR: RE: [ErrorSystem-devel] home page little update
> >>(son...@ss...)
> >>
> >>--__--__--
> >>
> >>Message: 1
> >>Reply-To: <bro...@fr...>
> >>From: "BrokenClock" <bro...@fr...>
> >>To: "Jacek Olszak" <e-k...@wp...>
> >>Cc: "ES-devel" <err...@li...>
> >>Date: Thu, 18 Dec 2003 15:40:20 +0100
> >>Subject: [ErrorSystem-devel] RE: RE: ErrorSystem - proposal
> >>
> >>Ok. Could you planned when this db layer should work for MySQL?
> >>I think we can developp ES with it if it supports MySQL, and waiting
> >>for =3D
> >>the
> >>support of the ohers databases.
> >>Maybe should you use a prefix for your functions, something like udbl
> >>(Universal DataBase Layer), so you should have udbl_connect and so
> >>on? or
> >>usql (Universal SQL Layer)?
> >>I think this particular feature should interessed other people, so
> >>maybe =3D
> >>you
> >>should find a way to published it more largely.
> >>About that, I may be able to test on Microsoft SQL Server soon (not
> >>my
> >>choice, you bet).
> >>
> >>Have fun, guys,
> >>
> >>Stephane
> >>
> >>> -----Message d'origine-----
> >>> De : Jacek Olszak [mailto:e-k...@wp...]
> >>> Envoy=3DE9 : jeudi 18 d=3DE9cembre 2003 13:07
> >>> A : bro...@fr...
> >>> Objet : RE: RE: ErrorSystem - proposal
> >>>
> >>>
> >>> Dnia 17-12-2003 o godz. 14:07 BrokenClock napisal(a):
> >>> > I think it could be a very good idea. But I don't know how to
> >>> do it, and ,
> >>> > in particular, how to test it.
> >>> I decide to write this class. It's very simple. It has methods
> >>> like connect(), executeQuery(), getResultsObject() etc. These
> >>> methods are similar to mysql_connect, mysql_query etc. but they
> >>> work on all databases. The class read from some.ini file the type
> >>> of database and when some of class method is invoke the class
> >>> decide what function to use (for example mysql_connect or
> >>>mssql_connect=3D
> >>).
> >>>
> >>>
> >>> --------------------------------------------------
> >>> 'Z=3DB3e zachowanie' wyrazem buntu m=3DB3odego pokolenia.
> >>> Widowisko muzyczne ju=3DBF do obejrzenia!
> >>> http://muzyka.wp.pl/imprezy.html?idn=3D3D799
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >>--__--__--
> >>
> >>Message: 2
> >>Date: Thu, 18 Dec 2003 08:53:48 -0600 (CST)
> >>Subject: Re: [ErrorSystem-devel] RE: RE: ErrorSystem - proposal
> >>From: son...@ss...
> >>To: bro...@fr...
> >>Cc: "Jacek Olszak" <e-k...@wp...>,
> >> "ES-devel" <err...@li...>
> >>
> >>Actaully, this is what I've been coding as a class. I'm not sure if
> >>you
> >>are familer with classes (the PHP documentation isn't very clear on
> >>them
> >>either), but basically, it's a list of functions. So this class could
> >>have
> >>function a(), and function b(). Now to access it I would do something
> >>liek
> >>this:
> >>
> >><?php
> >>class db {
> >> function a() {
> >> echo "test"
> >>}
> >>function b(){ echo test };
> >>}
> >>
> >>$db =3D new db
> >>$db->a // function a
> >>$db->b // function b
> >>}
> >>?>
> >>
> >>In other words, classes let someone make a function list, then it
> >>gets
> >>automatically prefixed. I don't like the idea of using MS-SQL, as
> >>it's
> >>syntax is not very compatiable with MySQL, and I don't have a PC I
> >>could
> >>use to help develop it. If we need to support both without goes
> >>through
> >>preg_replace hell to make them compatiable, we need to store the
> >>querys
> >>for each database in seperate files and then every time we need to
> >>use a
> >>query, we'll load it from the query file. That way, we can make it
> >>work
> >>with almost any database as all the queries could easily be changed,
> >>but
> >>it will make coding alot harder.
> >>
> >>> Ok. Could you planned when this db layer should work for MySQL?
> >>> I think we can developp ES with it if it supports MySQL, and waitin=
g
> >>>for
> >>> the
> >>> support of the ohers databases.
> >>> Maybe should you use a prefix for your functions, something like
> >>>udbl
> >>> (Universal DataBase Layer), so you should have udbl_connect and so
> >>>on? or
> >>> usql (Universal SQL Layer)?
> >>> I think this particular feature should interessed other people, so
> >>>maybe
> >>> you
> >>> should find a way to published it more largely.
> >>> About that, I may be able to test on Microsoft SQL Server soon (not
> >>>my
> >>> choice, you bet).
> >>>
> >>> Have fun, guys,
> >>>
> >>> Stephane
> >>>
> >>>> -----Message d'origine-----
> >>>> De : Jacek Olszak [mailto:e-k...@wp...]
> >>>> Envoy=E9 : jeudi 18 d=E9cembre 2003 13:07
> >>>> A : bro...@fr...
> >>>> Objet : RE: RE: ErrorSystem - proposal
> >>>>
> >>>>
> >>>> Dnia 17-12-2003 o godz. 14:07 BrokenClock napisal(a):
> >>>> > I think it could be a very good idea. But I don't know how to
> >>>> do it, and ,
> >>>> > in particular, how to test it.
> >>>> I decide to write this class. It's very simple. It has methods
> >>>> like connect(), executeQuery(), getResultsObject() etc. These
> >>>> methods are similar to mysql_connect, mysql_query etc. but they
> >>>> work on all databases. The class read from some.ini file the type
> >>>> of database and when some of class method is invoke the class
> >>>> decide what function to use (for example mysql_connect or
> >>>> mssql_connect).
> >>>>
> >>>>
> >>>> --------------------------------------------------
> >>>> 'Z=B3e zachowanie' wyrazem buntu m=B3odego pokolenia.
> >>>> Widowisko muzyczne ju=BF do obejrzenia!
> >>>> http://muzyka.wp.pl/imprezy.html?idn=3D799
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>> -------------------------------------------------------
> >>> 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
> >>>
> >>
> >>
> >>
> >>--__--__--
> >>
> >>Message: 3
> >>Reply-To: <bro...@fr...>
> >>From: "BrokenClock" <bro...@fr...>
> >>To: <son...@ss...>
> >>Cc: "ES-devel" <err...@li...>
> >>Subject: RE: TR: RE: [ErrorSystem-devel] home page little update
> >>Date: Thu, 18 Dec 2003 17:29:00 +0100
> >>
> >>About cvs : well, I had no time to test it again, but, I've check
> >>this pa=3D
> >>ge
> >>: http://cvs.sourceforge.net/viewcvs.py/errorsystem/ErrorSystem/ and
> >>I ca=3D
> >>n
> >>see now the files I have upload using TortoiseCVS feww weeks ago. So
> >>it
> >>seems working, but the page may take some time to update. And I can't
> >>understand why McTails haven't seen them when he browsed the tree.
> >>About my work : well, when I was hired here, we had a critical
> >>process,
> >>mixing VB and DOS batch files. It was a Mess! One day, we had another
> >>client. So we had to upgrade the process. So I put away this mess and
> >>wri=3D
> >>tte
> >>some PHP. This proccess is so critical for us that we need a very
> >>good er=3D
> >>ror
> >>management. So came the idear of ES. Thinking about, I found it was a
> >>goo=3D
> >>d
> >>idear, and may be useful for other people. And I thought that they
> >>could
> >>help me to make it better. So, I published on SourceForge. You know
> >>then =3D
> >>the
> >>history.
> >>
> >>I think I have now endly answer to most part of your mail. I hope I
> >>haven=3D
> >>'t
> >>forgot something.
> >>
> >>Have fun, guys,
> >>
> >>Stephane
> >>
> >>> -----Message d'origine-----
> >>> De : son...@ss... [mailto:son...@ss...]
> >>> Envoy=3DE9 : vendredi 12 d=3DE9cembre 2003 22:00
> >>> =3DC0 : bro...@fr...
> >>> Cc : ES-devel
> >>> Objet : Re: TR: RE: [ErrorSystem-devel] home page little update
> >>>
> >>>
> >>> Mostly right, but I was infering as MySQL as the default as it
> >>>supports
> >>> republiation, and has tools to make altering tables alot easier the=
n
> >>> SQLite. I think that what should be done is that a crontab event
> >>>(the
> >>> crontab is a way to run programs at a certian time on *NIXs). That
> >>>cron=3D
> >>tab
> >>> would do a data-only dump of the MySQL tables, backup the current
> >>>SQLit=3D
> >>e
> >>> database, and then recreate it using CREATE TABLE statements and th=
e
> >>> INSERT data. Also, you can use SQLite with PHP 4, it's available as
> >>>a P=3D
> >>ECL
> >>> module, and I have it running on my local copy of PHP. Anyway, as
> >>>now I
> >>> have some desgin, I'm going to write the Database API, so it will b=
e
> >>>ea=3D
> >>sy
> >>> to use the rollover. As an additional option, maybe we should add i=
t
> >>>so=3D
> >> it
> >>> can rollover to something else before SQLite, like a backup server =
?
> >>>Al=3D
> >>so,
> >>> what should the file layout for this problem be ?. I was going to
> >>>put t=3D
> >>he
> >>> database layer in, as well as the default schema:
> >>>
> >>> errorsystem/include/db/db-mysql.php
> >>> errorsystem/include/db/schema/base-mysql.sql
> >>>
> >>> Also, what does this mean for this project now that you can do it a=
t
> >>>yo=3D
> >>ur
> >>> workplace ? Will they adapt it once we get a working version ?.
> >>>Stephan=3D
> >>e,
> >>> can you please send me what code you have so I can get it into CVS.
> >>>
> >>> Also, here is some information about using WinCVS with SSH.
> >>> http://minimal.cx/wincvsssh.php
> >>>
> >>> However, once you run this part:
> >>> ---
> >>> Now log into the remote machine, and add this ID to the trusted
> >>>hosts f=3D
> >>ile
> >>> [1]:
> >>>
> >>> ssh -l <user> <remote_host>
> >>> cat id_dsa.pub >> .ssh/authorized_keys
> >>> rm id_dsa.pub
> >>> --
> >>>
> >>> Do this:
> >>> While still at the command prompt, type cat id_dsa.pub and copy the
> >>>lin=3D
> >>es
> >>> it generates (it should start with ssh-dss), and then copy that int=
o
> >>>yo=3D
> >>ur
> >>> Public Key Management on the SourceForge User page. Once it syncs
> >>>itsel=3D
> >>f
> >>> back to the CVS/Shell server, you should be able to get into CVS.
> >>>Then
> >>> follow the rest of the directions starting with wincvs setup.
> >>>
> >>> Two notes:
> >>> I'm loading this project into XCode (The Mac OS X Coder IDE), so
> >>>it's
> >>> going to put some additional files into the directory, but they
> >>>won't
> >>> interfer with anything (though we would have to remove them before
> >>>maki=3D
> >>ng
> >>> a release). Second, I'm going to write a Linux shell script that
> >>>will
> >>> strip out the .DS_Store files Mac OS X likes to leave behind, but
> >>>they
> >>> will be there, floating in the CVS files but you can safely ingore
> >>>them.
> >>> >
> >>> > Hi McTails,
> >>> >
> >>> >> -----Message d'origine-----
> >>> >> De : err...@li...
> >>> >> [mailto:err...@li...]De la part
> >>>de
> >>> >> son...@ss...
> >>> >> Envoy=3DE9 : vendredi 5 d=3DE9cembre 2003 21:32
> >>> >> =3DC0 : bro...@fr...
> >>> >> Cc : son...@ss...; ES-devel
> >>> >> Objet : RE: [ErrorSystem-devel] home page little update
> >>> >>
> >>> >>
> >>> >> It's McTails, sorry if I mispelt it :-P.
> >>> >
> >>> > Sorry, I have misunderstood...
> >>> >
> >>> >> I never figured that ES would be
> >>> >> used as a way to report MySQL errors as it already has a good
> >>> >> errorsystem.
> >>> >
> >>> > So do I. But I was thinking about ES should be used for advanced
> >>>erro=3D
> >>r
> >>> > reporting when a system uses MySQL. Imagine a PHP script, run
> >>>regular=3D
> >>y
> >>> > with
> >>> > the commandline (every 10 minutes for exemple), using MySQL to
> >>>store
> >>> > datas.
> >>> > The db server is down, so the query fails. PHP will prompt the
> >>> error, and
> >>> > it
> >>> > should be log with a redirection. And this error should run for a
> >>>lon=3D
> >>g
> >>> > time,
> >>> > since someone looks in the log file. I think ES should be used to
> >>>sen=3D
> >>d a
> >>> > mail to the admin on the first the error appends. In fact, it
> >>>exactel=3D
> >>y a
> >>> > feature I require. I should do that in the original script, but I
> >>>cou=3D
> >>ld
> >>> > also
> >>> > do everything I need in the script, but it should so better to do
> >>>thi=3D
> >>s
> >>> > with
> >>> > ES
> >>> >
> >>> >> Anyway, the CVS respiorty is empty and I find that a bunch of
> >>>Window=3D
> >>s
> >>> >> CVS
> >>> >> clients just don't report errors when using SSH.
> >>> > Shit!
> >>> >>WinCVS doesn't report
> >>> >> that it can't find putty, and it seems to appear working with
> >>> >> everything.
> >>> >> Remember that you must have your public key(s) upload to SF.net.
> >>> > How can I do that?
> >>> >> Also the
> >>> >> CVS script is not part of SF itself, it's a seperate one called
> >>>cvsw=3D
> >>eb
> >>> >> (this I know because I run a private local SF.net server).
> >>> > Nice!
> >>> >
> >>> >>What a
> >>> >> possiabile solution to do is to wait for PHP5, as it will be
> >>>includi=3D
> >>ng
> >>> >> SQLite, a file based SQL system that doesn't require a server.
> >>> > I don't know much about SQLite, but one of the soft I use (bacula
> >>>:
> >>> > www.bacula.org, a nice backup soft!), uses it, and it seems to
> >>> works well.
> >>> >>What could
> >>> >> be done is a. Data from MySQL is copied to SQLite at various
> >>> times b. We
> >>> >> use SQLite be default unless the user chooses otherwise c. We us=
e
> >>>it
> >>> >> seperate as a manual failback.
> >>> > So, if I understood well : SQLite as default, MySQL as an option,
> >>>wit=3D
> >>h a
> >>> > backup on SQLite. And we should begin with MySQL only, waiting
> >>> for PHP5. I
> >>> > think I can agreed that.
> >>> >> Regrads,
> >>> >> McTails
> >>> >> Regrads,
> >>> >> Sonic McTails
> >>> >
> >>> > 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=3D1278&alloc_id371&op=3DBFi=
ck
> >>> > _______________________________________________
> >>> > ErrorSystem-devel mailing list
> >>> > Err...@li...
> >>> > https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
> >>> >
> >>>
> >>>
> >>
> >>
> >>
> >>--__--__--
> >>
> >>Message: 4
> >>Date: Thu, 18 Dec 2003 14:15:26 -0600 (CST)
> >>Subject: RE: TR: RE: [ErrorSystem-devel] home page little update
> >>From: son...@ss...
> >>To: bro...@fr...
> >>Cc: son...@ss...,
> >> "ES-devel" <err...@li...>
> >>
> >>I need to move those files into folders, so once i get home today,
> >>I'll
> >>download them, and remove them from there, and put them in there
> >>proper
> >>place (unforanilty, CVS doesn't allow you to move files :( so it's a
> >>real
> >>pain). I should have the DB class done. One note: I was doing reading
> >>on
> >>proper file nameing, and it's recommend that all things are in
> >>lowercase
> >>for filenames, folders, and tables unless you have a good release as
> >>it
> >>appears to be a cheap marketing ploy if we did. Anyway, thats how I
> >>do my
> >>coding usually but I'll do it however you want it. Also, congras. on
> >>getting CVS to work :). I have no idea why I couldn't see it when I
> >>browsed the CVS repositry, but now my computer can see them and I've
> >>checked out the errorsystem project. Very important note when using
> >>CVS:
> >>leave good logs, other developers will love you for it. Anyway, since
> >>I
> >>will have so much free time, I might actually write enough code to
> >>get the
> >>backend working somewhat that we would primative system, but aleast
> >>we
> >>could prove it works. I don't think there would be any interface, but
> >>it
> >>would work :). I think that would be the first goal: getting a
> >>working
> >>system. THen we need to get a decent adminestrative database system,
> >>and
> >>from there, make it skinable so it can be enbeeded, etc.
> >>SMT
> >>
> >>> About cvs : well, I had no time to test it again, but, I've check
> >>>this
> >>> page
> >>> : http://cvs.sourceforge.net/viewcvs.py/errorsystem/ErrorSystem/ an=
d
> >>>I can
> >>> see now the files I have upload using TortoiseCVS feww weeks ago. S=
o
> >>>it
> >>> seems working, but the page may take some time to update. And I
> >>>can't
> >>> understand why McTails haven't seen them when he browsed the tree.
> >>> About my work : well, when I was hired here, we had a critical
> >>>process,
> >>> mixing VB and DOS batch files. It was a Mess! One day, we had
> >>>another
> >>> client. So we had to upgrade the process. So I put away this mess
> >>>and
> >>> writte
> >>> some PHP. This proccess is so critical for us that we need a very
> >>>good
> >>> error
> >>> management. So came the idear of ES. Thinking about, I found it was
> >>>a good
> >>> idear, and may be useful for other people. And I thought that they
> >>>could
> >>> help me to make it better. So, I published on SourceForge. You know
> >>>then
> >>> the
> >>> history.
> >>>
> >>> I think I have now endly answer to most part of your mail. I hope I
> >>> haven't
> >>> forgot something.
> >>>
> >>> Have fun, guys,
> >>>
> >>> Stephane
> >>>
> >>>> -----Message d'origine-----
> >>>> De : son...@ss... [mailto:son...@ss...=
]
> >>>> Envoy=E9 : vendredi 12 d=E9cembre 2003 22:00
> >>>> =C0 : bro...@fr...
> >>>> Cc : ES-devel
> >>>> Objet : Re: TR: RE: [ErrorSystem-devel] home page little update
> >>>>
> >>>>
> >>>> Mostly right, but I was infering as MySQL as the default as it
> >>>>supports
> >>>> republiation, and has tools to make altering tables alot easier th=
en
> >>>> SQLite. I think that what should be done is that a crontab event
> >>>>(the
> >>>> crontab is a way to run programs at a certian time on *NIXs). That
> >>>> crontab
> >>>> would do a data-only dump of the MySQL tables, backup the current
> >>>>SQLite
> >>>> database, and then recreate it using CREATE TABLE statements and t=
he
> >>>> INSERT data. Also, you can use SQLite with PHP 4, it's available a=
s
> >>>>a
> >>>> PECL
> >>>> module, and I have it running on my local copy of PHP. Anyway, as
> >>>>now I
> >>>> have some desgin, I'm going to write the Database API, so it will =
be
> >>>> easy
> >>>> to use the rollover. As an additional option, maybe we should add =
it
> >>>>so
> >>>> it
> >>>> can rollover to something else before SQLite, like a backup server=
?
> >>>> Also,
> >>>> what should the file layout for this problem be ?. I was going to
> >>>>put
> >>>> the
> >>>> database layer in, as well as the default schema:
> >>>>
> >>>> errorsystem/include/db/db-mysql.php
> >>>> errorsystem/include/db/schema/base-mysql.sql
> >>>>
> >>>> Also, what does this mean for this project now that you can do it =
at
> >>>> your
> >>>> workplace ? Will they adapt it once we get a working version ?.
> >>>> Stephane,
> >>>> can you please send me what code you have so I can get it into CVS.
> >>>>
> >>>> Also, here is some information about using WinCVS with SSH.
> >>>> http://minimal.cx/wincvsssh.php
> >>>>
> >>>> However, once you run this part:
> >>>> ---
> >>>> Now log into the remote machine, and add this ID to the trusted
> >>>>hosts
> >>>> file
> >>>> [1]:
> >>>>
> >>>> ssh -l <user> <remote_host>
> >>>> cat id_dsa.pub >> .ssh/authorized_keys
> >>>> rm id_dsa.pub
> >>>> --
> >>>>
> >>>> Do this:
> >>>> While still at the command prompt, type cat id_dsa.pub and copy th=
e
> >>>> lines
> >>>> it generates (it should start with ssh-dss), and then copy that in=
to
> >>>> your
> >>>> Public Key Management on the SourceForge User page. Once it syncs
> >>>>itself
> >>>> back to the CVS/Shell server, you should be able to get into CVS.
> >>>>Then
> >>>> follow the rest of the directions starting with wincvs setup.
> >>>>
> >>>> Two notes:
> >>>> I'm loading this project into XCode (The Mac OS X Coder IDE), so
> >>>>it's
> >>>> going to put some additional files into the directory, but they
> >>>>won't
> >>>> interfer with anything (though we would have to remove them before
> >>>> making
> >>>> a release). Second, I'm going to write a Linux shell script that
> >>>>will
> >>>> strip out the .DS_Store files Mac OS X likes to leave behind, but
> >>>>they
> >>>> will be there, floating in the CVS files but you can safely ingore
> >>>>them.
> >>>> >
> >>>> > Hi McTails,
> >>>> >
> >>>> >> -----Message d'origine-----
> >>>> >> De : err...@li...
> >>>> >> [mailto:err...@li...]De la par=
t
> >>>>de
> >>>> >> son...@ss...
> >>>> >> Envoy=E9 : vendredi 5 d=E9cembre 2003 21:32
> >>>> >> =C0 : bro...@fr...
> >>>> >> Cc : son...@ss...; ES-devel
> >>>> >> Objet : RE: [ErrorSystem-devel] home page little update
> >>>> >>
> >>>> >>
> >>>> >> It's McTails, sorry if I mispelt it :-P.
> >>>> >
> >>>> > Sorry, I have misunderstood...
> >>>> >
> >>>> >> I never figured that ES would be
> >>>> >> used as a way to report MySQL errors as it already has a good
> >>>> >> errorsystem.
> >>>> >
> >>>> > So do I. But I was thinking about ES should be used for advanced
> >>>>error
> >>>> > reporting when a system uses MySQL. Imagine a PHP script, run
> >>>>regulary
> >>>> > with
> >>>> > the commandline (every 10 minutes for exemple), using MySQL to
> >>>>store
> >>>> > datas.
> >>>> > The db server is down, so the query fails. PHP will prompt the
> >>>> error, and
> >>>> > it
> >>>> > should be log with a redirection. And this error should run for =
a
> >>>>long
> >>>> > time,
> >>>> > since someone looks in the log file. I think ES should be used t=
o
> >>>>send
> >>>> a
> >>>> > mail to the admin on the first the error appends. In fact, it
> >>>>exactely
> >>>> a
> >>>> > feature I require. I should do that in the original script, but =
I
> >>>> could
> >>>> > also
> >>>> > do everything I need in the script, but it should so better to d=
o
> >>>>this
> >>>> > with
> >>>> > ES
> >>>> >
> >>>> >> Anyway, the CVS respiorty is empty and I find that a bunch of
> >>>>Windows
> >>>> >> CVS
> >>>> >> clients just don't report errors when using SSH.
> >>>> > Shit!
> >>>> >>WinCVS doesn't report
> >>>> >> that it can't find putty, and it seems to appear working with
> >>>> >> everything.
> >>>> >> Remember that you must have your public key(s) upload to SF.net.
> >>>> > How can I do that?
> >>>> >> Also the
> >>>> >> CVS script is not part of SF itself, it's a seperate one called
> >>>> cvsweb
> >>>> >> (this I know because I run a private local SF.net server).
> >>>> > Nice!
> >>>> >
> >>>> >>What a
> >>>> >> possiabile solution to do is to wait for PHP5, as it will be
> >>>> including
> >>>> >> SQLite, a file based SQL system that doesn't require a server.
> >>>> > I don't know much about SQLite, but one of the soft I use (bacul=
a
> >>>>:
> >>>> > www.bacula.org, a nice backup soft!), uses it, and it seems to
> >>>> works well.
> >>>> >>What could
> >>>> >> be done is a. Data from MySQL is copied to SQLite at various
> >>>> times b. We
> >>>> >> use SQLite be default unless the user chooses otherwise c. We u=
se
> >>>>it
> >>>> >> seperate as a manual failback.
> >>>> > So, if I understood well : SQLite as default, MySQL as an option=
,
> >>>>with
> >>>> a
> >>>> > backup on SQLite. And we should begin with MySQL only, waiting
> >>>> for PHP5. I
> >>>> > think I can agreed that.
> >>>> >> Regrads,
> >>>> >> McTails
> >>>> >> Regrads,
> >>>> >> Sonic McTails
> >>>> >
> >>>> > 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
> >>>> >
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >>
> >>
> >>--__--__--
> >>
> >>_______________________________________________
> >>ErrorSystem-devel mailing list
> >>Err...@li...
> >>https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
> >>
> >>
> >>End of ErrorSystem-devel Digest
> >
> >
> >
> > -------------------------------------------------------
> > 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=3D1278&alloc_id=3D3371&op=3Dcli=
ck
> > _______________________________________________
> > 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
>
|
|
From: <son...@ss...> - 2003-12-21 06:14:58
|
I have my DB Class finished, but my laptop is currently not with me (I'm
with my cousins, and my laptop is home) I will get the files uploaded
ASAP. I have two versions, one using Mysql_ and one using mysqli_ as
mysql_ only works with version below 4.1.
> Maybe we can reach compatibility with different databases by using OOP
> STEP 1) Write classess for every needed database (for example -
> mysql_class.php, mssql_class.php, anydatabase_class.php...). Methods
> (functions) in these classes we have to name equal (for example,
> method db_connect() must be in every class). In these classes we may
> write methods:
> a) db_connect() - method to connect and login db, select database
> b) db_make_recordset() - method to execute an sql query.
> c) db_close() - to close connection
> Actually we have to set $dataset class variable which will store our
> result of sql query (its like '$dataset = mysql_query("select * from
> tbl")'). This variable we have to set in db_make_recordset() method.
>
> STEP 2) Use classes.
> We only write code:
> for mysql -
> include(mysql_class.php);
> $page = new page();
> $page->db_connect(host,user,password);
> $page->db_make_recordset(sqlquery);
> while ($row = mysql_fetch_array($page->dataset, MYSQL_ASSOC)) {
> printf ("ID: %s Name: %s", $row["id"], $row["name"]);
> }
> $page->close();
> for anydatabase -
> include(ANYDATABASE_class.php); // WE HAVE TO CHANGE ONLY THIS
> $page = new page_class();
> $page->db_connect(host,user,password);
> $page->db_make_recordset(sqlquery);
> while ($row = mysql_fetch_array($page->dataset, MYSQL_ASSOC)) {
> printf ("ID: %s Name: %s", $row["id"], $row["name"]);
> }
> $page->close();
>
> That's all of my proposition.
> Best Regards. nw.
>
>
> On Thu, 18 Dec 2003 20:07:20 -0800
> err...@li... wrote:
>>Send ErrorSystem-devel mailing list submissions to
>> err...@li...
>>
>>To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
>>or, via email, send a message with subject or body 'help' to
>> err...@li...
>>
>>You can reach the person managing the list at
>> err...@li...
>>
>>When replying, please edit your Subject line so it is more specific
>>than "Re: Contents of ErrorSystem-devel digest..."
>>
>>
>>Today's Topics:
>>
>> 1. RE: RE: ErrorSystem - proposal (BrokenClock)
>> 2. Re: RE: RE: ErrorSystem - proposal (son...@ss...)
>> 3. RE: TR: RE: [ErrorSystem-devel] home page little update
>>(BrokenClock)
>> 4. RE: TR: RE: [ErrorSystem-devel] home page little update
>>(son...@ss...)
>>
>>--__--__--
>>
>>Message: 1
>>Reply-To: <bro...@fr...>
>>From: "BrokenClock" <bro...@fr...>
>>To: "Jacek Olszak" <e-k...@wp...>
>>Cc: "ES-devel" <err...@li...>
>>Date: Thu, 18 Dec 2003 15:40:20 +0100
>>Subject: [ErrorSystem-devel] RE: RE: ErrorSystem - proposal
>>
>>Ok. Could you planned when this db layer should work for MySQL?
>>I think we can developp ES with it if it supports MySQL, and waiting
>>for =
>>the
>>support of the ohers databases.
>>Maybe should you use a prefix for your functions, something like udbl
>>(Universal DataBase Layer), so you should have udbl_connect and so
>>on? or
>>usql (Universal SQL Layer)?
>>I think this particular feature should interessed other people, so
>>maybe =
>>you
>>should find a way to published it more largely.
>>About that, I may be able to test on Microsoft SQL Server soon (not
>>my
>>choice, you bet).
>>
>>Have fun, guys,
>>
>>Stephane
>>
>>> -----Message d'origine-----
>>> De : Jacek Olszak [mailto:e-k...@wp...]
>>> Envoy=E9 : jeudi 18 d=E9cembre 2003 13:07
>>> A : bro...@fr...
>>> Objet : RE: RE: ErrorSystem - proposal
>>>
>>>
>>> Dnia 17-12-2003 o godz. 14:07 BrokenClock napisal(a):
>>> > I think it could be a very good idea. But I don't know how to
>>> do it, and ,
>>> > in particular, how to test it.
>>> I decide to write this class. It's very simple. It has methods
>>> like connect(), executeQuery(), getResultsObject() etc. These
>>> methods are similar to mysql_connect, mysql_query etc. but they
>>> work on all databases. The class read from some.ini file the type
>>> of database and when some of class method is invoke the class
>>> decide what function to use (for example mysql_connect or
>>>mssql_connect=
>>).
>>>
>>>
>>> --------------------------------------------------
>>> 'Z=B3e zachowanie' wyrazem buntu m=B3odego pokolenia.
>>> Widowisko muzyczne ju=BF do obejrzenia!
>>> http://muzyka.wp.pl/imprezy.html?idn=3D799
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>--__--__--
>>
>>Message: 2
>>Date: Thu, 18 Dec 2003 08:53:48 -0600 (CST)
>>Subject: Re: [ErrorSystem-devel] RE: RE: ErrorSystem - proposal
>>From: son...@ss...
>>To: bro...@fr...
>>Cc: "Jacek Olszak" <e-k...@wp...>,
>> "ES-devel" <err...@li...>
>>
>>Actaully, this is what I've been coding as a class. I'm not sure if
>>you
>>are familer with classes (the PHP documentation isn't very clear on
>>them
>>either), but basically, it's a list of functions. So this class could
>>have
>>function a(), and function b(). Now to access it I would do something
>>liek
>>this:
>>
>><?php
>>class db {
>> function a() {
>> echo "test"
>>}
>>function b(){ echo test };
>>}
>>
>>$db = new db
>>$db->a // function a
>>$db->b // function b
>>}
>>?>
>>
>>In other words, classes let someone make a function list, then it
>>gets
>>automatically prefixed. I don't like the idea of using MS-SQL, as
>>it's
>>syntax is not very compatiable with MySQL, and I don't have a PC I
>>could
>>use to help develop it. If we need to support both without goes
>>through
>>preg_replace hell to make them compatiable, we need to store the
>>querys
>>for each database in seperate files and then every time we need to
>>use a
>>query, we'll load it from the query file. That way, we can make it
>>work
>>with almost any database as all the queries could easily be changed,
>>but
>>it will make coding alot harder.
>>
>>> Ok. Could you planned when this db layer should work for MySQL?
>>> I think we can developp ES with it if it supports MySQL, and waiting
>>>for
>>> the
>>> support of the ohers databases.
>>> Maybe should you use a prefix for your functions, something like
>>>udbl
>>> (Universal DataBase Layer), so you should have udbl_connect and so
>>>on? or
>>> usql (Universal SQL Layer)?
>>> I think this particular feature should interessed other people, so
>>>maybe
>>> you
>>> should find a way to published it more largely.
>>> About that, I may be able to test on Microsoft SQL Server soon (not
>>>my
>>> choice, you bet).
>>>
>>> Have fun, guys,
>>>
>>> Stephane
>>>
>>>> -----Message d'origine-----
>>>> De : Jacek Olszak [mailto:e-k...@wp...]
>>>> Envoyé : jeudi 18 décembre 2003 13:07
>>>> A : bro...@fr...
>>>> Objet : RE: RE: ErrorSystem - proposal
>>>>
>>>>
>>>> Dnia 17-12-2003 o godz. 14:07 BrokenClock napisal(a):
>>>> > I think it could be a very good idea. But I don't know how to
>>>> do it, and ,
>>>> > in particular, how to test it.
>>>> I decide to write this class. It's very simple. It has methods
>>>> like connect(), executeQuery(), getResultsObject() etc. These
>>>> methods are similar to mysql_connect, mysql_query etc. but they
>>>> work on all databases. The class read from some.ini file the type
>>>> of database and when some of class method is invoke the class
>>>> decide what function to use (for example mysql_connect or
>>>> mssql_connect).
>>>>
>>>>
>>>> --------------------------------------------------
>>>> 'Z³e zachowanie' wyrazem buntu m³odego pokolenia.
>>>> Widowisko muzyczne ju¿ do obejrzenia!
>>>> http://muzyka.wp.pl/imprezy.html?idn=799
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> 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_id78&alloc_id371&op¿ick
>>> _______________________________________________
>>> ErrorSystem-devel mailing list
>>> Err...@li...
>>> https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
>>>
>>
>>
>>
>>--__--__--
>>
>>Message: 3
>>Reply-To: <bro...@fr...>
>>From: "BrokenClock" <bro...@fr...>
>>To: <son...@ss...>
>>Cc: "ES-devel" <err...@li...>
>>Subject: RE: TR: RE: [ErrorSystem-devel] home page little update
>>Date: Thu, 18 Dec 2003 17:29:00 +0100
>>
>>About cvs : well, I had no time to test it again, but, I've check
>>this pa=
>>ge
>>: http://cvs.sourceforge.net/viewcvs.py/errorsystem/ErrorSystem/ and
>>I ca=
>>n
>>see now the files I have upload using TortoiseCVS feww weeks ago. So
>>it
>>seems working, but the page may take some time to update. And I can't
>>understand why McTails haven't seen them when he browsed the tree.
>>About my work : well, when I was hired here, we had a critical
>>process,
>>mixing VB and DOS batch files. It was a Mess! One day, we had another
>>client. So we had to upgrade the process. So I put away this mess and
>>wri=
>>tte
>>some PHP. This proccess is so critical for us that we need a very
>>good er=
>>ror
>>management. So came the idear of ES. Thinking about, I found it was a
>>goo=
>>d
>>idear, and may be useful for other people. And I thought that they
>>could
>>help me to make it better. So, I published on SourceForge. You know
>>then =
>>the
>>history.
>>
>>I think I have now endly answer to most part of your mail. I hope I
>>haven=
>>'t
>>forgot something.
>>
>>Have fun, guys,
>>
>>Stephane
>>
>>> -----Message d'origine-----
>>> De : son...@ss... [mailto:son...@ss...]
>>> Envoy=E9 : vendredi 12 d=E9cembre 2003 22:00
>>> =C0 : bro...@fr...
>>> Cc : ES-devel
>>> Objet : Re: TR: RE: [ErrorSystem-devel] home page little update
>>>
>>>
>>> Mostly right, but I was infering as MySQL as the default as it
>>>supports
>>> republiation, and has tools to make altering tables alot easier then
>>> SQLite. I think that what should be done is that a crontab event
>>>(the
>>> crontab is a way to run programs at a certian time on *NIXs). That
>>>cron=
>>tab
>>> would do a data-only dump of the MySQL tables, backup the current
>>>SQLit=
>>e
>>> database, and then recreate it using CREATE TABLE statements and the
>>> INSERT data. Also, you can use SQLite with PHP 4, it's available as
>>>a P=
>>ECL
>>> module, and I have it running on my local copy of PHP. Anyway, as
>>>now I
>>> have some desgin, I'm going to write the Database API, so it will be
>>>ea=
>>sy
>>> to use the rollover. As an additional option, maybe we should add it
>>>so=
>> it
>>> can rollover to something else before SQLite, like a backup server ?
>>>Al=
>>so,
>>> what should the file layout for this problem be ?. I was going to
>>>put t=
>>he
>>> database layer in, as well as the default schema:
>>>
>>> errorsystem/include/db/db-mysql.php
>>> errorsystem/include/db/schema/base-mysql.sql
>>>
>>> Also, what does this mean for this project now that you can do it at
>>>yo=
>>ur
>>> workplace ? Will they adapt it once we get a working version ?.
>>>Stephan=
>>e,
>>> can you please send me what code you have so I can get it into CVS.
>>>
>>> Also, here is some information about using WinCVS with SSH.
>>> http://minimal.cx/wincvsssh.php
>>>
>>> However, once you run this part:
>>> ---
>>> Now log into the remote machine, and add this ID to the trusted
>>>hosts f=
>>ile
>>> [1]:
>>>
>>> ssh -l <user> <remote_host>
>>> cat id_dsa.pub >> .ssh/authorized_keys
>>> rm id_dsa.pub
>>> --
>>>
>>> Do this:
>>> While still at the command prompt, type cat id_dsa.pub and copy the
>>>lin=
>>es
>>> it generates (it should start with ssh-dss), and then copy that into
>>>yo=
>>ur
>>> Public Key Management on the SourceForge User page. Once it syncs
>>>itsel=
>>f
>>> back to the CVS/Shell server, you should be able to get into CVS.
>>>Then
>>> follow the rest of the directions starting with wincvs setup.
>>>
>>> Two notes:
>>> I'm loading this project into XCode (The Mac OS X Coder IDE), so
>>>it's
>>> going to put some additional files into the directory, but they
>>>won't
>>> interfer with anything (though we would have to remove them before
>>>maki=
>>ng
>>> a release). Second, I'm going to write a Linux shell script that
>>>will
>>> strip out the .DS_Store files Mac OS X likes to leave behind, but
>>>they
>>> will be there, floating in the CVS files but you can safely ingore
>>>them.
>>> >
>>> > Hi McTails,
>>> >
>>> >> -----Message d'origine-----
>>> >> De : err...@li...
>>> >> [mailto:err...@li...]De la part
>>>de
>>> >> son...@ss...
>>> >> Envoy=E9 : vendredi 5 d=E9cembre 2003 21:32
>>> >> =C0 : bro...@fr...
>>> >> Cc : son...@ss...; ES-devel
>>> >> Objet : RE: [ErrorSystem-devel] home page little update
>>> >>
>>> >>
>>> >> It's McTails, sorry if I mispelt it :-P.
>>> >
>>> > Sorry, I have misunderstood...
>>> >
>>> >> I never figured that ES would be
>>> >> used as a way to report MySQL errors as it already has a good
>>> >> errorsystem.
>>> >
>>> > So do I. But I was thinking about ES should be used for advanced
>>>erro=
>>r
>>> > reporting when a system uses MySQL. Imagine a PHP script, run
>>>regular=
>>y
>>> > with
>>> > the commandline (every 10 minutes for exemple), using MySQL to
>>>store
>>> > datas.
>>> > The db server is down, so the query fails. PHP will prompt the
>>> error, and
>>> > it
>>> > should be log with a redirection. And this error should run for a
>>>lon=
>>g
>>> > time,
>>> > since someone looks in the log file. I think ES should be used to
>>>sen=
>>d a
>>> > mail to the admin on the first the error appends. In fact, it
>>>exactel=
>>y a
>>> > feature I require. I should do that in the original script, but I
>>>cou=
>>ld
>>> > also
>>> > do everything I need in the script, but it should so better to do
>>>thi=
>>s
>>> > with
>>> > ES
>>> >
>>> >> Anyway, the CVS respiorty is empty and I find that a bunch of
>>>Window=
>>s
>>> >> CVS
>>> >> clients just don't report errors when using SSH.
>>> > Shit!
>>> >>WinCVS doesn't report
>>> >> that it can't find putty, and it seems to appear working with
>>> >> everything.
>>> >> Remember that you must have your public key(s) upload to SF.net.
>>> > How can I do that?
>>> >> Also the
>>> >> CVS script is not part of SF itself, it's a seperate one called
>>>cvsw=
>>eb
>>> >> (this I know because I run a private local SF.net server).
>>> > Nice!
>>> >
>>> >>What a
>>> >> possiabile solution to do is to wait for PHP5, as it will be
>>>includi=
>>ng
>>> >> SQLite, a file based SQL system that doesn't require a server.
>>> > I don't know much about SQLite, but one of the soft I use (bacula
>>>:
>>> > www.bacula.org, a nice backup soft!), uses it, and it seems to
>>> works well.
>>> >>What could
>>> >> be done is a. Data from MySQL is copied to SQLite at various
>>> times b. We
>>> >> use SQLite be default unless the user chooses otherwise c. We use
>>>it
>>> >> seperate as a manual failback.
>>> > So, if I understood well : SQLite as default, MySQL as an option,
>>>wit=
>>h a
>>> > backup on SQLite. And we should begin with MySQL only, waiting
>>> for PHP5. I
>>> > think I can agreed that.
>>> >> Regrads,
>>> >> McTails
>>> >> Regrads,
>>> >> Sonic McTails
>>> >
>>> > 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
>>> >
>>>
>>>
>>
>>
>>
>>--__--__--
>>
>>Message: 4
>>Date: Thu, 18 Dec 2003 14:15:26 -0600 (CST)
>>Subject: RE: TR: RE: [ErrorSystem-devel] home page little update
>>From: son...@ss...
>>To: bro...@fr...
>>Cc: son...@ss...,
>> "ES-devel" <err...@li...>
>>
>>I need to move those files into folders, so once i get home today,
>>I'll
>>download them, and remove them from there, and put them in there
>>proper
>>place (unforanilty, CVS doesn't allow you to move files :( so it's a
>>real
>>pain). I should have the DB class done. One note: I was doing reading
>>on
>>proper file nameing, and it's recommend that all things are in
>>lowercase
>>for filenames, folders, and tables unless you have a good release as
>>it
>>appears to be a cheap marketing ploy if we did. Anyway, thats how I
>>do my
>>coding usually but I'll do it however you want it. Also, congras. on
>>getting CVS to work :). I have no idea why I couldn't see it when I
>>browsed the CVS repositry, but now my computer can see them and I've
>>checked out the errorsystem project. Very important note when using
>>CVS:
>>leave good logs, other developers will love you for it. Anyway, since
>>I
>>will have so much free time, I might actually write enough code to
>>get the
>>backend working somewhat that we would primative system, but aleast
>>we
>>could prove it works. I don't think there would be any interface, but
>>it
>>would work :). I think that would be the first goal: getting a
>>working
>>system. THen we need to get a decent adminestrative database system,
>>and
>>from there, make it skinable so it can be enbeeded, etc.
>>SMT
>>
>>> About cvs : well, I had no time to test it again, but, I've check
>>>this
>>> page
>>> : http://cvs.sourceforge.net/viewcvs.py/errorsystem/ErrorSystem/ and
>>>I can
>>> see now the files I have upload using TortoiseCVS feww weeks ago. So
>>>it
>>> seems working, but the page may take some time to update. And I
>>>can't
>>> understand why McTails haven't seen them when he browsed the tree.
>>> About my work : well, when I was hired here, we had a critical
>>>process,
>>> mixing VB and DOS batch files. It was a Mess! One day, we had
>>>another
>>> client. So we had to upgrade the process. So I put away this mess
>>>and
>>> writte
>>> some PHP. This proccess is so critical for us that we need a very
>>>good
>>> error
>>> management. So came the idear of ES. Thinking about, I found it was
>>>a good
>>> idear, and may be useful for other people. And I thought that they
>>>could
>>> help me to make it better. So, I published on SourceForge. You know
>>>then
>>> the
>>> history.
>>>
>>> I think I have now endly answer to most part of your mail. I hope I
>>> haven't
>>> forgot something.
>>>
>>> Have fun, guys,
>>>
>>> Stephane
>>>
>>>> -----Message d'origine-----
>>>> De : son...@ss... [mailto:son...@ss...]
>>>> Envoyé : vendredi 12 décembre 2003 22:00
>>>> À : bro...@fr...
>>>> Cc : ES-devel
>>>> Objet : Re: TR: RE: [ErrorSystem-devel] home page little update
>>>>
>>>>
>>>> Mostly right, but I was infering as MySQL as the default as it
>>>>supports
>>>> republiation, and has tools to make altering tables alot easier then
>>>> SQLite. I think that what should be done is that a crontab event
>>>>(the
>>>> crontab is a way to run programs at a certian time on *NIXs). That
>>>> crontab
>>>> would do a data-only dump of the MySQL tables, backup the current
>>>>SQLite
>>>> database, and then recreate it using CREATE TABLE statements and the
>>>> INSERT data. Also, you can use SQLite with PHP 4, it's available as
>>>>a
>>>> PECL
>>>> module, and I have it running on my local copy of PHP. Anyway, as
>>>>now I
>>>> have some desgin, I'm going to write the Database API, so it will be
>>>> easy
>>>> to use the rollover. As an additional option, maybe we should add it
>>>>so
>>>> it
>>>> can rollover to something else before SQLite, like a backup server ?
>>>> Also,
>>>> what should the file layout for this problem be ?. I was going to
>>>>put
>>>> the
>>>> database layer in, as well as the default schema:
>>>>
>>>> errorsystem/include/db/db-mysql.php
>>>> errorsystem/include/db/schema/base-mysql.sql
>>>>
>>>> Also, what does this mean for this project now that you can do it at
>>>> your
>>>> workplace ? Will they adapt it once we get a working version ?.
>>>> Stephane,
>>>> can you please send me what code you have so I can get it into CVS.
>>>>
>>>> Also, here is some information about using WinCVS with SSH.
>>>> http://minimal.cx/wincvsssh.php
>>>>
>>>> However, once you run this part:
>>>> ---
>>>> Now log into the remote machine, and add this ID to the trusted
>>>>hosts
>>>> file
>>>> [1]:
>>>>
>>>> ssh -l <user> <remote_host>
>>>> cat id_dsa.pub >> .ssh/authorized_keys
>>>> rm id_dsa.pub
>>>> --
>>>>
>>>> Do this:
>>>> While still at the command prompt, type cat id_dsa.pub and copy the
>>>> lines
>>>> it generates (it should start with ssh-dss), and then copy that into
>>>> your
>>>> Public Key Management on the SourceForge User page. Once it syncs
>>>>itself
>>>> back to the CVS/Shell server, you should be able to get into CVS.
>>>>Then
>>>> follow the rest of the directions starting with wincvs setup.
>>>>
>>>> Two notes:
>>>> I'm loading this project into XCode (The Mac OS X Coder IDE), so
>>>>it's
>>>> going to put some additional files into the directory, but they
>>>>won't
>>>> interfer with anything (though we would have to remove them before
>>>> making
>>>> a release). Second, I'm going to write a Linux shell script that
>>>>will
>>>> strip out the .DS_Store files Mac OS X likes to leave behind, but
>>>>they
>>>> will be there, floating in the CVS files but you can safely ingore
>>>>them.
>>>> >
>>>> > Hi McTails,
>>>> >
>>>> >> -----Message d'origine-----
>>>> >> De : err...@li...
>>>> >> [mailto:err...@li...]De la part
>>>>de
>>>> >> son...@ss...
>>>> >> Envoyé : vendredi 5 décembre 2003 21:32
>>>> >> À : bro...@fr...
>>>> >> Cc : son...@ss...; ES-devel
>>>> >> Objet : RE: [ErrorSystem-devel] home page little update
>>>> >>
>>>> >>
>>>> >> It's McTails, sorry if I mispelt it :-P.
>>>> >
>>>> > Sorry, I have misunderstood...
>>>> >
>>>> >> I never figured that ES would be
>>>> >> used as a way to report MySQL errors as it already has a good
>>>> >> errorsystem.
>>>> >
>>>> > So do I. But I was thinking about ES should be used for advanced
>>>>error
>>>> > reporting when a system uses MySQL. Imagine a PHP script, run
>>>>regulary
>>>> > with
>>>> > the commandline (every 10 minutes for exemple), using MySQL to
>>>>store
>>>> > datas.
>>>> > The db server is down, so the query fails. PHP will prompt the
>>>> error, and
>>>> > it
>>>> > should be log with a redirection. And this error should run for a
>>>>long
>>>> > time,
>>>> > since someone looks in the log file. I think ES should be used to
>>>>send
>>>> a
>>>> > mail to the admin on the first the error appends. In fact, it
>>>>exactely
>>>> a
>>>> > feature I require. I should do that in the original script, but I
>>>> could
>>>> > also
>>>> > do everything I need in the script, but it should so better to do
>>>>this
>>>> > with
>>>> > ES
>>>> >
>>>> >> Anyway, the CVS respiorty is empty and I find that a bunch of
>>>>Windows
>>>> >> CVS
>>>> >> clients just don't report errors when using SSH.
>>>> > Shit!
>>>> >>WinCVS doesn't report
>>>> >> that it can't find putty, and it seems to appear working with
>>>> >> everything.
>>>> >> Remember that you must have your public key(s) upload to SF.net.
>>>> > How can I do that?
>>>> >> Also the
>>>> >> CVS script is not part of SF itself, it's a seperate one called
>>>> cvsweb
>>>> >> (this I know because I run a private local SF.net server).
>>>> > Nice!
>>>> >
>>>> >>What a
>>>> >> possiabile solution to do is to wait for PHP5, as it will be
>>>> including
>>>> >> SQLite, a file based SQL system that doesn't require a server.
>>>> > I don't know much about SQLite, but one of the soft I use (bacula
>>>>:
>>>> > www.bacula.org, a nice backup soft!), uses it, and it seems to
>>>> works well.
>>>> >>What could
>>>> >> be done is a. Data from MySQL is copied to SQLite at various
>>>> times b. We
>>>> >> use SQLite be default unless the user chooses otherwise c. We use
>>>>it
>>>> >> seperate as a manual failback.
>>>> > So, if I understood well : SQLite as default, MySQL as an option,
>>>>with
>>>> a
>>>> > backup on SQLite. And we should begin with MySQL only, waiting
>>>> for PHP5. I
>>>> > think I can agreed that.
>>>> >> Regrads,
>>>> >> McTails
>>>> >> Regrads,
>>>> >> Sonic McTails
>>>> >
>>>> > 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_id78&alloc_id371&op¿ick
>>>> > _______________________________________________
>>>> > ErrorSystem-devel mailing list
>>>> > Err...@li...
>>>> > https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
>>>> >
>>>>
>>>>
>>>
>>>
>>
>>
>>
>>
>>--__--__--
>>
>>_______________________________________________
>>ErrorSystem-devel mailing list
>>Err...@li...
>>https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
>>
>>
>>End of ErrorSystem-devel Digest
>
>
>
> -------------------------------------------------------
> 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_id=3371&op=click
> _______________________________________________
> ErrorSystem-devel mailing list
> Err...@li...
> https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
>
|
|
From: nw <bi...@ra...> - 2003-12-19 11:07:20
|
Maybe we can reach compatibility with different databases by using OOP
STEP 1) Write classess for every needed database (for example -
mysql_class.php, mssql_class.php, anydatabase_class.php...). Methods
(functions) in these classes we have to name equal (for example,
method db_connect() must be in every class). In these classes we may
write methods:
a) db_connect() - method to connect and login db, select database
b) db_make_recordset() - method to execute an sql query.
c) db_close() - to close connection
Actually we have to set $dataset class variable which will store our
result of sql query (its like '$dataset = mysql_query("select * from
tbl")'). This variable we have to set in db_make_recordset() method.
STEP 2) Use classes.
We only write code:
for mysql -
include(mysql_class.php);
$page = new page();
$page->db_connect(host,user,password);
$page->db_make_recordset(sqlquery);
while ($row = mysql_fetch_array($page->dataset, MYSQL_ASSOC)) {
printf ("ID: %s Name: %s", $row["id"], $row["name"]);
}
$page->close();
for anydatabase -
include(ANYDATABASE_class.php); // WE HAVE TO CHANGE ONLY THIS
$page = new page_class();
$page->db_connect(host,user,password);
$page->db_make_recordset(sqlquery);
while ($row = mysql_fetch_array($page->dataset, MYSQL_ASSOC)) {
printf ("ID: %s Name: %s", $row["id"], $row["name"]);
}
$page->close();
That's all of my proposition.
Best Regards. nw.
On Thu, 18 Dec 2003 20:07:20 -0800
err...@li... wrote:
>Send ErrorSystem-devel mailing list submissions to
> err...@li...
>
>To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
>or, via email, send a message with subject or body 'help' to
> err...@li...
>
>You can reach the person managing the list at
> err...@li...
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of ErrorSystem-devel digest..."
>
>
>Today's Topics:
>
> 1. RE: RE: ErrorSystem - proposal (BrokenClock)
> 2. Re: RE: RE: ErrorSystem - proposal (son...@ss...)
> 3. RE: TR: RE: [ErrorSystem-devel] home page little update
>(BrokenClock)
> 4. RE: TR: RE: [ErrorSystem-devel] home page little update
>(son...@ss...)
>
>--__--__--
>
>Message: 1
>Reply-To: <bro...@fr...>
>From: "BrokenClock" <bro...@fr...>
>To: "Jacek Olszak" <e-k...@wp...>
>Cc: "ES-devel" <err...@li...>
>Date: Thu, 18 Dec 2003 15:40:20 +0100
>Subject: [ErrorSystem-devel] RE: RE: ErrorSystem - proposal
>
>Ok. Could you planned when this db layer should work for MySQL?
>I think we can developp ES with it if it supports MySQL, and waiting
>for =
>the
>support of the ohers databases.
>Maybe should you use a prefix for your functions, something like udbl
>(Universal DataBase Layer), so you should have udbl_connect and so
>on? or
>usql (Universal SQL Layer)?
>I think this particular feature should interessed other people, so
>maybe =
>you
>should find a way to published it more largely.
>About that, I may be able to test on Microsoft SQL Server soon (not
>my
>choice, you bet).
>
>Have fun, guys,
>
>Stephane
>
>> -----Message d'origine-----
>> De : Jacek Olszak [mailto:e-k...@wp...]
>> Envoy=E9 : jeudi 18 d=E9cembre 2003 13:07
>> A : bro...@fr...
>> Objet : RE: RE: ErrorSystem - proposal
>>
>>
>> Dnia 17-12-2003 o godz. 14:07 BrokenClock napisal(a):
>> > I think it could be a very good idea. But I don't know how to
>> do it, and ,
>> > in particular, how to test it.
>> I decide to write this class. It's very simple. It has methods
>> like connect(), executeQuery(), getResultsObject() etc. These
>> methods are similar to mysql_connect, mysql_query etc. but they
>> work on all databases. The class read from some.ini file the type
>> of database and when some of class method is invoke the class
>> decide what function to use (for example mysql_connect or
>>mssql_connect=
>).
>>
>>
>> --------------------------------------------------
>> 'Z=B3e zachowanie' wyrazem buntu m=B3odego pokolenia.
>> Widowisko muzyczne ju=BF do obejrzenia!
>> http://muzyka.wp.pl/imprezy.html?idn=3D799
>>
>>
>>
>>
>>
>
>
>
>--__--__--
>
>Message: 2
>Date: Thu, 18 Dec 2003 08:53:48 -0600 (CST)
>Subject: Re: [ErrorSystem-devel] RE: RE: ErrorSystem - proposal
>From: son...@ss...
>To: bro...@fr...
>Cc: "Jacek Olszak" <e-k...@wp...>,
> "ES-devel" <err...@li...>
>
>Actaully, this is what I've been coding as a class. I'm not sure if
>you
>are familer with classes (the PHP documentation isn't very clear on
>them
>either), but basically, it's a list of functions. So this class could
>have
>function a(), and function b(). Now to access it I would do something
>liek
>this:
>
><?php
>class db {
> function a() {
> echo "test"
>}
>function b(){ echo test };
>}
>
>$db = new db
>$db->a // function a
>$db->b // function b
>}
>?>
>
>In other words, classes let someone make a function list, then it
>gets
>automatically prefixed. I don't like the idea of using MS-SQL, as
>it's
>syntax is not very compatiable with MySQL, and I don't have a PC I
>could
>use to help develop it. If we need to support both without goes
>through
>preg_replace hell to make them compatiable, we need to store the
>querys
>for each database in seperate files and then every time we need to
>use a
>query, we'll load it from the query file. That way, we can make it
>work
>with almost any database as all the queries could easily be changed,
>but
>it will make coding alot harder.
>
>> Ok. Could you planned when this db layer should work for MySQL?
>> I think we can developp ES with it if it supports MySQL, and waiting
>>for
>> the
>> support of the ohers databases.
>> Maybe should you use a prefix for your functions, something like
>>udbl
>> (Universal DataBase Layer), so you should have udbl_connect and so
>>on? or
>> usql (Universal SQL Layer)?
>> I think this particular feature should interessed other people, so
>>maybe
>> you
>> should find a way to published it more largely.
>> About that, I may be able to test on Microsoft SQL Server soon (not
>>my
>> choice, you bet).
>>
>> Have fun, guys,
>>
>> Stephane
>>
>>> -----Message d'origine-----
>>> De : Jacek Olszak [mailto:e-k...@wp...]
>>> Envoyй : jeudi 18 dйcembre 2003 13:07
>>> A : bro...@fr...
>>> Objet : RE: RE: ErrorSystem - proposal
>>>
>>>
>>> Dnia 17-12-2003 o godz. 14:07 BrokenClock napisal(a):
>>> > I think it could be a very good idea. But I don't know how to
>>> do it, and ,
>>> > in particular, how to test it.
>>> I decide to write this class. It's very simple. It has methods
>>> like connect(), executeQuery(), getResultsObject() etc. These
>>> methods are similar to mysql_connect, mysql_query etc. but they
>>> work on all databases. The class read from some.ini file the type
>>> of database and when some of class method is invoke the class
>>> decide what function to use (for example mysql_connect or
>>> mssql_connect).
>>>
>>>
>>> --------------------------------------------------
>>> 'Zіe zachowanie' wyrazem buntu mіodego pokolenia.
>>> Widowisko muzyczne juї do obejrzenia!
>>> http://muzyka.wp.pl/imprezy.html?idn=799
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>> -------------------------------------------------------
>> 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_id78&alloc_id371&opїick
>> _______________________________________________
>> ErrorSystem-devel mailing list
>> Err...@li...
>> https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
>>
>
>
>
>--__--__--
>
>Message: 3
>Reply-To: <bro...@fr...>
>From: "BrokenClock" <bro...@fr...>
>To: <son...@ss...>
>Cc: "ES-devel" <err...@li...>
>Subject: RE: TR: RE: [ErrorSystem-devel] home page little update
>Date: Thu, 18 Dec 2003 17:29:00 +0100
>
>About cvs : well, I had no time to test it again, but, I've check
>this pa=
>ge
>: http://cvs.sourceforge.net/viewcvs.py/errorsystem/ErrorSystem/ and
>I ca=
>n
>see now the files I have upload using TortoiseCVS feww weeks ago. So
>it
>seems working, but the page may take some time to update. And I can't
>understand why McTails haven't seen them when he browsed the tree.
>About my work : well, when I was hired here, we had a critical
>process,
>mixing VB and DOS batch files. It was a Mess! One day, we had another
>client. So we had to upgrade the process. So I put away this mess and
>wri=
>tte
>some PHP. This proccess is so critical for us that we need a very
>good er=
>ror
>management. So came the idear of ES. Thinking about, I found it was a
>goo=
>d
>idear, and may be useful for other people. And I thought that they
>could
>help me to make it better. So, I published on SourceForge. You know
>then =
>the
>history.
>
>I think I have now endly answer to most part of your mail. I hope I
>haven=
>'t
>forgot something.
>
>Have fun, guys,
>
>Stephane
>
>> -----Message d'origine-----
>> De : son...@ss... [mailto:son...@ss...]
>> Envoy=E9 : vendredi 12 d=E9cembre 2003 22:00
>> =C0 : bro...@fr...
>> Cc : ES-devel
>> Objet : Re: TR: RE: [ErrorSystem-devel] home page little update
>>
>>
>> Mostly right, but I was infering as MySQL as the default as it
>>supports
>> republiation, and has tools to make altering tables alot easier then
>> SQLite. I think that what should be done is that a crontab event
>>(the
>> crontab is a way to run programs at a certian time on *NIXs). That
>>cron=
>tab
>> would do a data-only dump of the MySQL tables, backup the current
>>SQLit=
>e
>> database, and then recreate it using CREATE TABLE statements and the
>> INSERT data. Also, you can use SQLite with PHP 4, it's available as
>>a P=
>ECL
>> module, and I have it running on my local copy of PHP. Anyway, as
>>now I
>> have some desgin, I'm going to write the Database API, so it will be
>>ea=
>sy
>> to use the rollover. As an additional option, maybe we should add it
>>so=
> it
>> can rollover to something else before SQLite, like a backup server ?
>>Al=
>so,
>> what should the file layout for this problem be ?. I was going to
>>put t=
>he
>> database layer in, as well as the default schema:
>>
>> errorsystem/include/db/db-mysql.php
>> errorsystem/include/db/schema/base-mysql.sql
>>
>> Also, what does this mean for this project now that you can do it at
>>yo=
>ur
>> workplace ? Will they adapt it once we get a working version ?.
>>Stephan=
>e,
>> can you please send me what code you have so I can get it into CVS.
>>
>> Also, here is some information about using WinCVS with SSH.
>> http://minimal.cx/wincvsssh.php
>>
>> However, once you run this part:
>> ---
>> Now log into the remote machine, and add this ID to the trusted
>>hosts f=
>ile
>> [1]:
>>
>> ssh -l <user> <remote_host>
>> cat id_dsa.pub >> .ssh/authorized_keys
>> rm id_dsa.pub
>> --
>>
>> Do this:
>> While still at the command prompt, type cat id_dsa.pub and copy the
>>lin=
>es
>> it generates (it should start with ssh-dss), and then copy that into
>>yo=
>ur
>> Public Key Management on the SourceForge User page. Once it syncs
>>itsel=
>f
>> back to the CVS/Shell server, you should be able to get into CVS.
>>Then
>> follow the rest of the directions starting with wincvs setup.
>>
>> Two notes:
>> I'm loading this project into XCode (The Mac OS X Coder IDE), so
>>it's
>> going to put some additional files into the directory, but they
>>won't
>> interfer with anything (though we would have to remove them before
>>maki=
>ng
>> a release). Second, I'm going to write a Linux shell script that
>>will
>> strip out the .DS_Store files Mac OS X likes to leave behind, but
>>they
>> will be there, floating in the CVS files but you can safely ingore
>>them.
>> >
>> > Hi McTails,
>> >
>> >> -----Message d'origine-----
>> >> De : err...@li...
>> >> [mailto:err...@li...]De la part
>>de
>> >> son...@ss...
>> >> Envoy=E9 : vendredi 5 d=E9cembre 2003 21:32
>> >> =C0 : bro...@fr...
>> >> Cc : son...@ss...; ES-devel
>> >> Objet : RE: [ErrorSystem-devel] home page little update
>> >>
>> >>
>> >> It's McTails, sorry if I mispelt it :-P.
>> >
>> > Sorry, I have misunderstood...
>> >
>> >> I never figured that ES would be
>> >> used as a way to report MySQL errors as it already has a good
>> >> errorsystem.
>> >
>> > So do I. But I was thinking about ES should be used for advanced
>>erro=
>r
>> > reporting when a system uses MySQL. Imagine a PHP script, run
>>regular=
>y
>> > with
>> > the commandline (every 10 minutes for exemple), using MySQL to
>>store
>> > datas.
>> > The db server is down, so the query fails. PHP will prompt the
>> error, and
>> > it
>> > should be log with a redirection. And this error should run for a
>>lon=
>g
>> > time,
>> > since someone looks in the log file. I think ES should be used to
>>sen=
>d a
>> > mail to the admin on the first the error appends. In fact, it
>>exactel=
>y a
>> > feature I require. I should do that in the original script, but I
>>cou=
>ld
>> > also
>> > do everything I need in the script, but it should so better to do
>>thi=
>s
>> > with
>> > ES
>> >
>> >> Anyway, the CVS respiorty is empty and I find that a bunch of
>>Window=
>s
>> >> CVS
>> >> clients just don't report errors when using SSH.
>> > Shit!
>> >>WinCVS doesn't report
>> >> that it can't find putty, and it seems to appear working with
>> >> everything.
>> >> Remember that you must have your public key(s) upload to SF.net.
>> > How can I do that?
>> >> Also the
>> >> CVS script is not part of SF itself, it's a seperate one called
>>cvsw=
>eb
>> >> (this I know because I run a private local SF.net server).
>> > Nice!
>> >
>> >>What a
>> >> possiabile solution to do is to wait for PHP5, as it will be
>>includi=
>ng
>> >> SQLite, a file based SQL system that doesn't require a server.
>> > I don't know much about SQLite, but one of the soft I use (bacula
>>:
>> > www.bacula.org, a nice backup soft!), uses it, and it seems to
>> works well.
>> >>What could
>> >> be done is a. Data from MySQL is copied to SQLite at various
>> times b. We
>> >> use SQLite be default unless the user chooses otherwise c. We use
>>it
>> >> seperate as a manual failback.
>> > So, if I understood well : SQLite as default, MySQL as an option,
>>wit=
>h a
>> > backup on SQLite. And we should begin with MySQL only, waiting
>> for PHP5. I
>> > think I can agreed that.
>> >> Regrads,
>> >> McTails
>> >> Regrads,
>> >> Sonic McTails
>> >
>> > 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
>> >
>>
>>
>
>
>
>--__--__--
>
>Message: 4
>Date: Thu, 18 Dec 2003 14:15:26 -0600 (CST)
>Subject: RE: TR: RE: [ErrorSystem-devel] home page little update
>From: son...@ss...
>To: bro...@fr...
>Cc: son...@ss...,
> "ES-devel" <err...@li...>
>
>I need to move those files into folders, so once i get home today,
>I'll
>download them, and remove them from there, and put them in there
>proper
>place (unforanilty, CVS doesn't allow you to move files :( so it's a
>real
>pain). I should have the DB class done. One note: I was doing reading
>on
>proper file nameing, and it's recommend that all things are in
>lowercase
>for filenames, folders, and tables unless you have a good release as
>it
>appears to be a cheap marketing ploy if we did. Anyway, thats how I
>do my
>coding usually but I'll do it however you want it. Also, congras. on
>getting CVS to work :). I have no idea why I couldn't see it when I
>browsed the CVS repositry, but now my computer can see them and I've
>checked out the errorsystem project. Very important note when using
>CVS:
>leave good logs, other developers will love you for it. Anyway, since
>I
>will have so much free time, I might actually write enough code to
>get the
>backend working somewhat that we would primative system, but aleast
>we
>could prove it works. I don't think there would be any interface, but
>it
>would work :). I think that would be the first goal: getting a
>working
>system. THen we need to get a decent adminestrative database system,
>and
>from there, make it skinable so it can be enbeeded, etc.
>SMT
>
>> About cvs : well, I had no time to test it again, but, I've check
>>this
>> page
>> : http://cvs.sourceforge.net/viewcvs.py/errorsystem/ErrorSystem/ and
>>I can
>> see now the files I have upload using TortoiseCVS feww weeks ago. So
>>it
>> seems working, but the page may take some time to update. And I
>>can't
>> understand why McTails haven't seen them when he browsed the tree.
>> About my work : well, when I was hired here, we had a critical
>>process,
>> mixing VB and DOS batch files. It was a Mess! One day, we had
>>another
>> client. So we had to upgrade the process. So I put away this mess
>>and
>> writte
>> some PHP. This proccess is so critical for us that we need a very
>>good
>> error
>> management. So came the idear of ES. Thinking about, I found it was
>>a good
>> idear, and may be useful for other people. And I thought that they
>>could
>> help me to make it better. So, I published on SourceForge. You know
>>then
>> the
>> history.
>>
>> I think I have now endly answer to most part of your mail. I hope I
>> haven't
>> forgot something.
>>
>> Have fun, guys,
>>
>> Stephane
>>
>>> -----Message d'origine-----
>>> De : son...@ss... [mailto:son...@ss...]
>>> Envoyй : vendredi 12 dйcembre 2003 22:00
>>> А : bro...@fr...
>>> Cc : ES-devel
>>> Objet : Re: TR: RE: [ErrorSystem-devel] home page little update
>>>
>>>
>>> Mostly right, but I was infering as MySQL as the default as it
>>>supports
>>> republiation, and has tools to make altering tables alot easier then
>>> SQLite. I think that what should be done is that a crontab event
>>>(the
>>> crontab is a way to run programs at a certian time on *NIXs). That
>>> crontab
>>> would do a data-only dump of the MySQL tables, backup the current
>>>SQLite
>>> database, and then recreate it using CREATE TABLE statements and the
>>> INSERT data. Also, you can use SQLite with PHP 4, it's available as
>>>a
>>> PECL
>>> module, and I have it running on my local copy of PHP. Anyway, as
>>>now I
>>> have some desgin, I'm going to write the Database API, so it will be
>>> easy
>>> to use the rollover. As an additional option, maybe we should add it
>>>so
>>> it
>>> can rollover to something else before SQLite, like a backup server ?
>>> Also,
>>> what should the file layout for this problem be ?. I was going to
>>>put
>>> the
>>> database layer in, as well as the default schema:
>>>
>>> errorsystem/include/db/db-mysql.php
>>> errorsystem/include/db/schema/base-mysql.sql
>>>
>>> Also, what does this mean for this project now that you can do it at
>>> your
>>> workplace ? Will they adapt it once we get a working version ?.
>>> Stephane,
>>> can you please send me what code you have so I can get it into CVS.
>>>
>>> Also, here is some information about using WinCVS with SSH.
>>> http://minimal.cx/wincvsssh.php
>>>
>>> However, once you run this part:
>>> ---
>>> Now log into the remote machine, and add this ID to the trusted
>>>hosts
>>> file
>>> [1]:
>>>
>>> ssh -l <user> <remote_host>
>>> cat id_dsa.pub >> .ssh/authorized_keys
>>> rm id_dsa.pub
>>> --
>>>
>>> Do this:
>>> While still at the command prompt, type cat id_dsa.pub and copy the
>>> lines
>>> it generates (it should start with ssh-dss), and then copy that into
>>> your
>>> Public Key Management on the SourceForge User page. Once it syncs
>>>itself
>>> back to the CVS/Shell server, you should be able to get into CVS.
>>>Then
>>> follow the rest of the directions starting with wincvs setup.
>>>
>>> Two notes:
>>> I'm loading this project into XCode (The Mac OS X Coder IDE), so
>>>it's
>>> going to put some additional files into the directory, but they
>>>won't
>>> interfer with anything (though we would have to remove them before
>>> making
>>> a release). Second, I'm going to write a Linux shell script that
>>>will
>>> strip out the .DS_Store files Mac OS X likes to leave behind, but
>>>they
>>> will be there, floating in the CVS files but you can safely ingore
>>>them.
>>> >
>>> > Hi McTails,
>>> >
>>> >> -----Message d'origine-----
>>> >> De : err...@li...
>>> >> [mailto:err...@li...]De la part
>>>de
>>> >> son...@ss...
>>> >> Envoyй : vendredi 5 dйcembre 2003 21:32
>>> >> А : bro...@fr...
>>> >> Cc : son...@ss...; ES-devel
>>> >> Objet : RE: [ErrorSystem-devel] home page little update
>>> >>
>>> >>
>>> >> It's McTails, sorry if I mispelt it :-P.
>>> >
>>> > Sorry, I have misunderstood...
>>> >
>>> >> I never figured that ES would be
>>> >> used as a way to report MySQL errors as it already has a good
>>> >> errorsystem.
>>> >
>>> > So do I. But I was thinking about ES should be used for advanced
>>>error
>>> > reporting when a system uses MySQL. Imagine a PHP script, run
>>>regulary
>>> > with
>>> > the commandline (every 10 minutes for exemple), using MySQL to
>>>store
>>> > datas.
>>> > The db server is down, so the query fails. PHP will prompt the
>>> error, and
>>> > it
>>> > should be log with a redirection. And this error should run for a
>>>long
>>> > time,
>>> > since someone looks in the log file. I think ES should be used to
>>>send
>>> a
>>> > mail to the admin on the first the error appends. In fact, it
>>>exactely
>>> a
>>> > feature I require. I should do that in the original script, but I
>>> could
>>> > also
>>> > do everything I need in the script, but it should so better to do
>>>this
>>> > with
>>> > ES
>>> >
>>> >> Anyway, the CVS respiorty is empty and I find that a bunch of
>>>Windows
>>> >> CVS
>>> >> clients just don't report errors when using SSH.
>>> > Shit!
>>> >>WinCVS doesn't report
>>> >> that it can't find putty, and it seems to appear working with
>>> >> everything.
>>> >> Remember that you must have your public key(s) upload to SF.net.
>>> > How can I do that?
>>> >> Also the
>>> >> CVS script is not part of SF itself, it's a seperate one called
>>> cvsweb
>>> >> (this I know because I run a private local SF.net server).
>>> > Nice!
>>> >
>>> >>What a
>>> >> possiabile solution to do is to wait for PHP5, as it will be
>>> including
>>> >> SQLite, a file based SQL system that doesn't require a server.
>>> > I don't know much about SQLite, but one of the soft I use (bacula
>>>:
>>> > www.bacula.org, a nice backup soft!), uses it, and it seems to
>>> works well.
>>> >>What could
>>> >> be done is a. Data from MySQL is copied to SQLite at various
>>> times b. We
>>> >> use SQLite be default unless the user chooses otherwise c. We use
>>>it
>>> >> seperate as a manual failback.
>>> > So, if I understood well : SQLite as default, MySQL as an option,
>>>with
>>> a
>>> > backup on SQLite. And we should begin with MySQL only, waiting
>>> for PHP5. I
>>> > think I can agreed that.
>>> >> Regrads,
>>> >> McTails
>>> >> Regrads,
>>> >> Sonic McTails
>>> >
>>> > 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_id78&alloc_id371&opїick
>>> > _______________________________________________
>>> > ErrorSystem-devel mailing list
>>> > Err...@li...
>>> > https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
>>> >
>>>
>>>
>>
>>
>
>
>
>
>--__--__--
>
>_______________________________________________
>ErrorSystem-devel mailing list
>Err...@li...
>https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
>
>
>End of ErrorSystem-devel Digest
|
|
From: Jacek M. O. <s1...@ph...> - 2003-12-19 10:19:48
|
That's the file. Sorry, but I have some problems with sending files using lynx and www mail |
|
From: BrokenClock <bro...@fr...> - 2003-12-19 10:11:51
|
Have you post it somewhere? We may have a look at it, and make comments, suggestions, and all. I think that you haven't read my last mail about classes, just posted thi= s morning (about 10 GMT+1). I have suggest to use DBlayer as an object. I think we should not have many code to add for this feature. Have fun, Stephane > -----Message d'origine----- > De : err...@li... > [mailto:err...@li...]De la part de > Jacek Michal Olszak > Envoy=E9 : vendredi 19 d=E9cembre 2003 10:44 > =C0 : err...@li... > Objet : [ErrorSystem-devel] I've a simple Database.class.php > > > Now it only support MySQL, but I'll add another bases support in the > future. > The class read configuration from setup/database.inc.php file. In this > file must be defined variables: $server, $user, $password, $port, > $dataBase and $type > > > > > > ------------------------------------------------------- > 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 > |
|
From: Jacek M. O. <s1...@ph...> - 2003-12-19 09:44:24
|
Now it only support MySQL, but I'll add another bases support in the future. The class read configuration from setup/database.inc.php file. In this file must be defined variables: $server, $user, $password, $port, $dataBase and $type |
|
From: BrokenClock <bro...@fr...> - 2003-12-19 08:44:26
|
About classes : I haven't check the official PHP doc about them, but I ha=
ve
read something in a book. Well, it was a french book, so I will directly
translate technical words frmm french, but I'm sure it wouldn't be the ri=
ght
words.
Class is a fundamental concept of object programming. PHP is a *near* obj=
ect
programming langage. It means that it doesn't support all the features
required to be a object programming langage, but must of them. In
particular, it doesn't support polymorphism (I can't remeber what it is).
In object programming, classes are abstract descriptions of objects. An
class puts together properties and functions called, in this case, method=
s
of the object or the class. When you created an object, you must tell whi=
ch
is its class. A special method, called the builder, is automaticaly
executed. The builder has the same name as the class.
Deeper, you have mother-classes and daughter-classes (in french, classes =
are
female, so in english, it should be father and son). When you begin to
describ a daughter-class, it is the same as its mother. This is heritage.
Then you add or modify methods. So, beginning with a class, you should ma=
ke
a tree.
One of the features of object programming does not support well, is the
heritage of the builder method. It seems that a daughter-class doesn't
inherit the builder method of its mother. As I understand it, I think thi=
s
is because PHP uses the name of the class to execute its builder method, =
and
the daughter-class has not the same name than its mother, so PHP doesn't
execute the mother builder. I think that the daughter inherits the builde=
r
method, but PHP doesn't recognize it as a builder, but just as a method.
To conclude, after this little boring lesson (I hope that there is someo=
ne
here that didn't know all that before, and I beg the pardon of the others
(well, I asked for beginner programmers, after all)), I think it is a ver=
y
good idea to use class for DB Layer. But I must add that it will be so mu=
ch
better if we take advantage of all features of object programming, and no=
t
just consider class as a list of functions. I think we can make a db real
object class. So the db layer should be able to simplify the connect to m=
ore
then one db.
Well, to show, I take an example of what I mean. Imagine that we have
already coded the db class, and see how we could use it.
<?
$MyFirstDb=3Dnew db("MySQL", "localhost", "user", "password");
//this line should create the object, set the typ as MySQL, the adress of
the MySQL server, and all)
//may we connect in the builder? Let's say so, or this example. So this l=
ine
should be suffisant to create the connection.
$MyFirstDB=3D>CreateDB("ErrorSystem");
//this line should create the database "ErrorSystem" on the db server.
//well, the things seems to be a little messy, and we have to make the
things clear : there may be a confusion between server and db...
$MySecondDb=3Dnew db("ProgresSQL", "192.168.45.12", "user", "pass");
//well, I think I don't have to explain more
?>
In this case, we should be able to manipulate the first and the second db
very simply, without confusing, and a very clear code.
Well, I have a little work now, so tell me what you think and
Have fun, guys,
Stephane
> -----Message d'origine-----
> De : err...@li...
> [mailto:err...@li...]De la part de
> son...@ss...
> Envoy=E9 : jeudi 18 d=E9cembre 2003 15:54
> =C0 : bro...@fr...
> Cc : Jacek Olszak; ES-devel
> Objet : Re: [ErrorSystem-devel] RE: RE: ErrorSystem - proposal
>
>
> Actaully, this is what I've been coding as a class. I'm not sure if you
> are familer with classes (the PHP documentation isn't very clear on the=
m
> either), but basically, it's a list of functions. So this class could h=
ave
> function a(), and function b(). Now to access it I would do something l=
iek
> this:
>
> <?php
> class db {
> function a() {
> echo "test"
> }
> function b(){ echo test };
> }
>
> $db =3D new db
> $db->a // function a
> $db->b // function b
> }
> ?>
>
> In other words, classes let someone make a function list, then it gets
> automatically prefixed. I don't like the idea of using MS-SQL, as it's
> syntax is not very compatiable with MySQL, and I don't have a PC I coul=
d
> use to help develop it. If we need to support both without goes through
> preg_replace hell to make them compatiable, we need to store the querys
> for each database in seperate files and then every time we need to use =
a
> query, we'll load it from the query file. That way, we can make it work
> with almost any database as all the queries could easily be changed, bu=
t
> it will make coding alot harder.
>
> > Ok. Could you planned when this db layer should work for MySQL?
> > I think we can developp ES with it if it supports MySQL, and waiting =
for
> > the
> > support of the ohers databases.
> > Maybe should you use a prefix for your functions, something like udbl
> > (Universal DataBase Layer), so you should have udbl_connect and
> so on? or
> > usql (Universal SQL Layer)?
> > I think this particular feature should interessed other people, so ma=
ybe
> > you
> > should find a way to published it more largely.
> > About that, I may be able to test on Microsoft SQL Server soon (not m=
y
> > choice, you bet).
> >
> > Have fun, guys,
> >
> > Stephane
> >
> >> -----Message d'origine-----
> >> De : Jacek Olszak [mailto:e-k...@wp...]
> >> Envoy=E9 : jeudi 18 d=E9cembre 2003 13:07
> >> A : bro...@fr...
> >> Objet : RE: RE: ErrorSystem - proposal
> >>
> >>
> >> Dnia 17-12-2003 o godz. 14:07 BrokenClock napisal(a):
> >> > I think it could be a very good idea. But I don't know how to
> >> do it, and ,
> >> > in particular, how to test it.
> >> I decide to write this class. It's very simple. It has methods
> >> like connect(), executeQuery(), getResultsObject() etc. These
> >> methods are similar to mysql_connect, mysql_query etc. but they
> >> work on all databases. The class read from some.ini file the type
> >> of database and when some of class method is invoke the class
> >> decide what function to use (for example mysql_connect or
> >> mssql_connect).
> >>
> >>
> >> --------------------------------------------------
> >> 'Z=B3e zachowanie' wyrazem buntu m=B3odego pokolenia.
> >> Widowisko muzyczne ju=BF do obejrzenia!
> >> http://muzyka.wp.pl/imprezy.html?idn=3D799
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> > -------------------------------------------------------
> > 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
>
|
|
From: <son...@ss...> - 2003-12-18 20:15:33
|
I need to move those files into folders, so once i get home today, I'll download them, and remove them from there, and put them in there proper place (unforanilty, CVS doesn't allow you to move files :( so it's a real pain). I should have the DB class done. One note: I was doing reading on proper file nameing, and it's recommend that all things are in lowercase for filenames, folders, and tables unless you have a good release as it appears to be a cheap marketing ploy if we did. Anyway, thats how I do my coding usually but I'll do it however you want it. Also, congras. on getting CVS to work :). I have no idea why I couldn't see it when I browsed the CVS repositry, but now my computer can see them and I've checked out the errorsystem project. Very important note when using CVS: leave good logs, other developers will love you for it. Anyway, since I will have so much free time, I might actually write enough code to get the backend working somewhat that we would primative system, but aleast we could prove it works. I don't think there would be any interface, but it would work :). I think that would be the first goal: getting a working system. THen we need to get a decent adminestrative database system, and from there, make it skinable so it can be enbeeded, etc. SMT > About cvs : well, I had no time to test it again, but, I've check this > page > : http://cvs.sourceforge.net/viewcvs.py/errorsystem/ErrorSystem/ and I can > see now the files I have upload using TortoiseCVS feww weeks ago. So it > seems working, but the page may take some time to update. And I can't > understand why McTails haven't seen them when he browsed the tree. > About my work : well, when I was hired here, we had a critical process, > mixing VB and DOS batch files. It was a Mess! One day, we had another > client. So we had to upgrade the process. So I put away this mess and > writte > some PHP. This proccess is so critical for us that we need a very good > error > management. So came the idear of ES. Thinking about, I found it was a good > idear, and may be useful for other people. And I thought that they could > help me to make it better. So, I published on SourceForge. You know then > the > history. > > I think I have now endly answer to most part of your mail. I hope I > haven't > forgot something. > > Have fun, guys, > > Stephane > >> -----Message d'origine----- >> De : son...@ss... [mailto:son...@ss...] >> Envoyé : vendredi 12 décembre 2003 22:00 >> À : bro...@fr... >> Cc : ES-devel >> Objet : Re: TR: RE: [ErrorSystem-devel] home page little update >> >> >> Mostly right, but I was infering as MySQL as the default as it supports >> republiation, and has tools to make altering tables alot easier then >> SQLite. I think that what should be done is that a crontab event (the >> crontab is a way to run programs at a certian time on *NIXs). That >> crontab >> would do a data-only dump of the MySQL tables, backup the current SQLite >> database, and then recreate it using CREATE TABLE statements and the >> INSERT data. Also, you can use SQLite with PHP 4, it's available as a >> PECL >> module, and I have it running on my local copy of PHP. Anyway, as now I >> have some desgin, I'm going to write the Database API, so it will be >> easy >> to use the rollover. As an additional option, maybe we should add it so >> it >> can rollover to something else before SQLite, like a backup server ? >> Also, >> what should the file layout for this problem be ?. I was going to put >> the >> database layer in, as well as the default schema: >> >> errorsystem/include/db/db-mysql.php >> errorsystem/include/db/schema/base-mysql.sql >> >> Also, what does this mean for this project now that you can do it at >> your >> workplace ? Will they adapt it once we get a working version ?. >> Stephane, >> can you please send me what code you have so I can get it into CVS. >> >> Also, here is some information about using WinCVS with SSH. >> http://minimal.cx/wincvsssh.php >> >> However, once you run this part: >> --- >> Now log into the remote machine, and add this ID to the trusted hosts >> file >> [1]: >> >> ssh -l <user> <remote_host> >> cat id_dsa.pub >> .ssh/authorized_keys >> rm id_dsa.pub >> -- >> >> Do this: >> While still at the command prompt, type cat id_dsa.pub and copy the >> lines >> it generates (it should start with ssh-dss), and then copy that into >> your >> Public Key Management on the SourceForge User page. Once it syncs itself >> back to the CVS/Shell server, you should be able to get into CVS. Then >> follow the rest of the directions starting with wincvs setup. >> >> Two notes: >> I'm loading this project into XCode (The Mac OS X Coder IDE), so it's >> going to put some additional files into the directory, but they won't >> interfer with anything (though we would have to remove them before >> making >> a release). Second, I'm going to write a Linux shell script that will >> strip out the .DS_Store files Mac OS X likes to leave behind, but they >> will be there, floating in the CVS files but you can safely ingore them. >> > >> > Hi McTails, >> > >> >> -----Message d'origine----- >> >> De : err...@li... >> >> [mailto:err...@li...]De la part de >> >> son...@ss... >> >> Envoyé : vendredi 5 décembre 2003 21:32 >> >> À : bro...@fr... >> >> Cc : son...@ss...; ES-devel >> >> Objet : RE: [ErrorSystem-devel] home page little update >> >> >> >> >> >> It's McTails, sorry if I mispelt it :-P. >> > >> > Sorry, I have misunderstood... >> > >> >> I never figured that ES would be >> >> used as a way to report MySQL errors as it already has a good >> >> errorsystem. >> > >> > So do I. But I was thinking about ES should be used for advanced error >> > reporting when a system uses MySQL. Imagine a PHP script, run regulary >> > with >> > the commandline (every 10 minutes for exemple), using MySQL to store >> > datas. >> > The db server is down, so the query fails. PHP will prompt the >> error, and >> > it >> > should be log with a redirection. And this error should run for a long >> > time, >> > since someone looks in the log file. I think ES should be used to send >> a >> > mail to the admin on the first the error appends. In fact, it exactely >> a >> > feature I require. I should do that in the original script, but I >> could >> > also >> > do everything I need in the script, but it should so better to do this >> > with >> > ES >> > >> >> Anyway, the CVS respiorty is empty and I find that a bunch of Windows >> >> CVS >> >> clients just don't report errors when using SSH. >> > Shit! >> >>WinCVS doesn't report >> >> that it can't find putty, and it seems to appear working with >> >> everything. >> >> Remember that you must have your public key(s) upload to SF.net. >> > How can I do that? >> >> Also the >> >> CVS script is not part of SF itself, it's a seperate one called >> cvsweb >> >> (this I know because I run a private local SF.net server). >> > Nice! >> > >> >>What a >> >> possiabile solution to do is to wait for PHP5, as it will be >> including >> >> SQLite, a file based SQL system that doesn't require a server. >> > I don't know much about SQLite, but one of the soft I use (bacula : >> > www.bacula.org, a nice backup soft!), uses it, and it seems to >> works well. >> >>What could >> >> be done is a. Data from MySQL is copied to SQLite at various >> times b. We >> >> use SQLite be default unless the user chooses otherwise c. We use it >> >> seperate as a manual failback. >> > So, if I understood well : SQLite as default, MySQL as an option, with >> a >> > backup on SQLite. And we should begin with MySQL only, waiting >> for PHP5. I >> > think I can agreed that. >> >> Regrads, >> >> McTails >> >> Regrads, >> >> Sonic McTails >> > >> > 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_id78&alloc_id371&op¿ick >> > _______________________________________________ >> > ErrorSystem-devel mailing list >> > Err...@li... >> > https://lists.sourceforge.net/lists/listinfo/errorsystem-devel >> > >> >> > > |
|
From: BrokenClock <bro...@fr...> - 2003-12-18 16:29:40
|
About cvs : well, I had no time to test it again, but, I've check this pa= ge : http://cvs.sourceforge.net/viewcvs.py/errorsystem/ErrorSystem/ and I ca= n see now the files I have upload using TortoiseCVS feww weeks ago. So it seems working, but the page may take some time to update. And I can't understand why McTails haven't seen them when he browsed the tree. About my work : well, when I was hired here, we had a critical process, mixing VB and DOS batch files. It was a Mess! One day, we had another client. So we had to upgrade the process. So I put away this mess and wri= tte some PHP. This proccess is so critical for us that we need a very good er= ror management. So came the idear of ES. Thinking about, I found it was a goo= d idear, and may be useful for other people. And I thought that they could help me to make it better. So, I published on SourceForge. You know then = the history. I think I have now endly answer to most part of your mail. I hope I haven= 't forgot something. Have fun, guys, Stephane > -----Message d'origine----- > De : son...@ss... [mailto:son...@ss...] > Envoy=E9 : vendredi 12 d=E9cembre 2003 22:00 > =C0 : bro...@fr... > Cc : ES-devel > Objet : Re: TR: RE: [ErrorSystem-devel] home page little update > > > Mostly right, but I was infering as MySQL as the default as it supports > republiation, and has tools to make altering tables alot easier then > SQLite. I think that what should be done is that a crontab event (the > crontab is a way to run programs at a certian time on *NIXs). That cron= tab > would do a data-only dump of the MySQL tables, backup the current SQLit= e > database, and then recreate it using CREATE TABLE statements and the > INSERT data. Also, you can use SQLite with PHP 4, it's available as a P= ECL > module, and I have it running on my local copy of PHP. Anyway, as now I > have some desgin, I'm going to write the Database API, so it will be ea= sy > to use the rollover. As an additional option, maybe we should add it so= it > can rollover to something else before SQLite, like a backup server ? Al= so, > what should the file layout for this problem be ?. I was going to put t= he > database layer in, as well as the default schema: > > errorsystem/include/db/db-mysql.php > errorsystem/include/db/schema/base-mysql.sql > > Also, what does this mean for this project now that you can do it at yo= ur > workplace ? Will they adapt it once we get a working version ?. Stephan= e, > can you please send me what code you have so I can get it into CVS. > > Also, here is some information about using WinCVS with SSH. > http://minimal.cx/wincvsssh.php > > However, once you run this part: > --- > Now log into the remote machine, and add this ID to the trusted hosts f= ile > [1]: > > ssh -l <user> <remote_host> > cat id_dsa.pub >> .ssh/authorized_keys > rm id_dsa.pub > -- > > Do this: > While still at the command prompt, type cat id_dsa.pub and copy the lin= es > it generates (it should start with ssh-dss), and then copy that into yo= ur > Public Key Management on the SourceForge User page. Once it syncs itsel= f > back to the CVS/Shell server, you should be able to get into CVS. Then > follow the rest of the directions starting with wincvs setup. > > Two notes: > I'm loading this project into XCode (The Mac OS X Coder IDE), so it's > going to put some additional files into the directory, but they won't > interfer with anything (though we would have to remove them before maki= ng > a release). Second, I'm going to write a Linux shell script that will > strip out the .DS_Store files Mac OS X likes to leave behind, but they > will be there, floating in the CVS files but you can safely ingore them. > > > > Hi McTails, > > > >> -----Message d'origine----- > >> De : err...@li... > >> [mailto:err...@li...]De la part de > >> son...@ss... > >> Envoy=E9 : vendredi 5 d=E9cembre 2003 21:32 > >> =C0 : bro...@fr... > >> Cc : son...@ss...; ES-devel > >> Objet : RE: [ErrorSystem-devel] home page little update > >> > >> > >> It's McTails, sorry if I mispelt it :-P. > > > > Sorry, I have misunderstood... > > > >> I never figured that ES would be > >> used as a way to report MySQL errors as it already has a good > >> errorsystem. > > > > So do I. But I was thinking about ES should be used for advanced erro= r > > reporting when a system uses MySQL. Imagine a PHP script, run regular= y > > with > > the commandline (every 10 minutes for exemple), using MySQL to store > > datas. > > The db server is down, so the query fails. PHP will prompt the > error, and > > it > > should be log with a redirection. And this error should run for a lon= g > > time, > > since someone looks in the log file. I think ES should be used to sen= d a > > mail to the admin on the first the error appends. In fact, it exactel= y a > > feature I require. I should do that in the original script, but I cou= ld > > also > > do everything I need in the script, but it should so better to do thi= s > > with > > ES > > > >> Anyway, the CVS respiorty is empty and I find that a bunch of Window= s > >> CVS > >> clients just don't report errors when using SSH. > > Shit! > >>WinCVS doesn't report > >> that it can't find putty, and it seems to appear working with > >> everything. > >> Remember that you must have your public key(s) upload to SF.net. > > How can I do that? > >> Also the > >> CVS script is not part of SF itself, it's a seperate one called cvsw= eb > >> (this I know because I run a private local SF.net server). > > Nice! > > > >>What a > >> possiabile solution to do is to wait for PHP5, as it will be includi= ng > >> SQLite, a file based SQL system that doesn't require a server. > > I don't know much about SQLite, but one of the soft I use (bacula : > > www.bacula.org, a nice backup soft!), uses it, and it seems to > works well. > >>What could > >> be done is a. Data from MySQL is copied to SQLite at various > times b. We > >> use SQLite be default unless the user chooses otherwise c. We use it > >> seperate as a manual failback. > > So, if I understood well : SQLite as default, MySQL as an option, wit= h a > > backup on SQLite. And we should begin with MySQL only, waiting > for PHP5. I > > think I can agreed that. > >> Regrads, > >> McTails > >> Regrads, > >> Sonic McTails > > > > 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 > > > > |
|
From: <son...@ss...> - 2003-12-18 14:53:54
|
Actaully, this is what I've been coding as a class. I'm not sure if you
are familer with classes (the PHP documentation isn't very clear on them
either), but basically, it's a list of functions. So this class could have
function a(), and function b(). Now to access it I would do something liek
this:
<?php
class db {
function a() {
echo "test"
}
function b(){ echo test };
}
$db = new db
$db->a // function a
$db->b // function b
}
?>
In other words, classes let someone make a function list, then it gets
automatically prefixed. I don't like the idea of using MS-SQL, as it's
syntax is not very compatiable with MySQL, and I don't have a PC I could
use to help develop it. If we need to support both without goes through
preg_replace hell to make them compatiable, we need to store the querys
for each database in seperate files and then every time we need to use a
query, we'll load it from the query file. That way, we can make it work
with almost any database as all the queries could easily be changed, but
it will make coding alot harder.
> Ok. Could you planned when this db layer should work for MySQL?
> I think we can developp ES with it if it supports MySQL, and waiting for
> the
> support of the ohers databases.
> Maybe should you use a prefix for your functions, something like udbl
> (Universal DataBase Layer), so you should have udbl_connect and so on? or
> usql (Universal SQL Layer)?
> I think this particular feature should interessed other people, so maybe
> you
> should find a way to published it more largely.
> About that, I may be able to test on Microsoft SQL Server soon (not my
> choice, you bet).
>
> Have fun, guys,
>
> Stephane
>
>> -----Message d'origine-----
>> De : Jacek Olszak [mailto:e-k...@wp...]
>> Envoyé : jeudi 18 décembre 2003 13:07
>> A : bro...@fr...
>> Objet : RE: RE: ErrorSystem - proposal
>>
>>
>> Dnia 17-12-2003 o godz. 14:07 BrokenClock napisal(a):
>> > I think it could be a very good idea. But I don't know how to
>> do it, and ,
>> > in particular, how to test it.
>> I decide to write this class. It's very simple. It has methods
>> like connect(), executeQuery(), getResultsObject() etc. These
>> methods are similar to mysql_connect, mysql_query etc. but they
>> work on all databases. The class read from some.ini file the type
>> of database and when some of class method is invoke the class
>> decide what function to use (for example mysql_connect or
>> mssql_connect).
>>
>>
>> --------------------------------------------------
>> 'Z³e zachowanie' wyrazem buntu m³odego pokolenia.
>> Widowisko muzyczne ju¿ do obejrzenia!
>> http://muzyka.wp.pl/imprezy.html?idn=799
>>
>>
>>
>>
>>
>
>
>
> -------------------------------------------------------
> 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_id78&alloc_id371&op¿ick
> _______________________________________________
> ErrorSystem-devel mailing list
> Err...@li...
> https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
>
|
|
From: BrokenClock <bro...@fr...> - 2003-12-18 14:40:57
|
Ok. Could you planned when this db layer should work for MySQL? I think we can developp ES with it if it supports MySQL, and waiting for = the support of the ohers databases. Maybe should you use a prefix for your functions, something like udbl (Universal DataBase Layer), so you should have udbl_connect and so on? or usql (Universal SQL Layer)? I think this particular feature should interessed other people, so maybe = you should find a way to published it more largely. About that, I may be able to test on Microsoft SQL Server soon (not my choice, you bet). Have fun, guys, Stephane > -----Message d'origine----- > De : Jacek Olszak [mailto:e-k...@wp...] > Envoy=E9 : jeudi 18 d=E9cembre 2003 13:07 > A : bro...@fr... > Objet : RE: RE: ErrorSystem - proposal > > > Dnia 17-12-2003 o godz. 14:07 BrokenClock napisal(a): > > I think it could be a very good idea. But I don't know how to > do it, and , > > in particular, how to test it. > I decide to write this class. It's very simple. It has methods > like connect(), executeQuery(), getResultsObject() etc. These > methods are similar to mysql_connect, mysql_query etc. but they > work on all databases. The class read from some.ini file the type > of database and when some of class method is invoke the class > decide what function to use (for example mysql_connect or mssql_connect= ). > > > -------------------------------------------------- > 'Z=B3e zachowanie' wyrazem buntu m=B3odego pokolenia. > Widowisko muzyczne ju=BF do obejrzenia! > http://muzyka.wp.pl/imprezy.html?idn=3D799 > > > > > |
|
From: BrokenClock <bro...@fr...> - 2003-12-17 13:28:56
|
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 > |
|
From: <son...@ss...> - 2003-12-16 21:17:52
|
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 fixing 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 = 3 would work fine. As the the DBA class, I should hopefully also get that finished by weeks end. Stephane, could you please 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 here knows how to use CVS, as once we really getting coding, it's going to get 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é : mardi 16 décembre 2003 08:59 >> À : 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=YOURSYSTEM&errnum=25&lg=en"). SYSTEM=YOURSYSTEM >> is the better way than by example SYSTEM=21 (if systemID field value >> 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 deflg >> >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 the >> >yoursystem-ini table, and the default langage used by ES and all the >> >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 think? >> >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é : lundi 15 décembre 2003 10:00 >> >> À : 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 table >> >> 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, Ðóññêèé, >> >>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-ErrorLevels >> >> table) >> >> InternalCode >> >> (In this table i have some doubts about errorName to use by special >> >> 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 error >> >> 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 received >> >> >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) instead >> >>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 lot >> >>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_id78&alloc_id371&op¿ick > _______________________________________________ > ErrorSystem-devel mailing list > Err...@li... > https://lists.sourceforge.net/lists/listinfo/errorsystem-devel > |
|
From: BrokenClock <bro...@fr...> - 2003-12-16 14:04:44
|
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=3DYOURS= YSTEM > is the better way than by example SYSTEM=3D21 (if systemID field value > 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 deflg > >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 the > >yoursystem-ini table, and the default langage used by ES and all the > >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 think? > >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 table > >> 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-ErrorLevels > >> table) > >> InternalCode > >> (In this table i have some doubts about errorName to use by special > >> 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 error > >> 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 received > >> >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) instead > >>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 lot > >>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 > >> > > |
|
From: BrokenClock <bro...@fr...> - 2003-12-16 13:22:42
|
-----Message d'origine----- De : BrokenClock [mailto:bro...@fr...] Envoy=E9 : lundi 15 d=E9cembre 2003 19:19 =C0 : son...@ss... Objet : RE: [ErrorSystem-devel] NOT NULLs in DB ? I think we should make our code as portable as we can, it is one of my ma= jor request, so I suggest to "write the checking code then have it fall back = on the db". > -----Message d'origine----- > De : err...@li... > [mailto:err...@li...]De la part de > son...@ss... > Envoy=E9 : lundi 15 d=E9cembre 2003 17:00 > =C0 : err...@li... > Objet : [ErrorSystem-devel] NOT NULLs in DB ? > > > Should we depend on MySQL to enforce empty fields ? Currently, this mig= ht > be a good idea, but other databases (notably Oracle and postgreSQL) don= 't > handle NULLs too well, so it might be better to write the checking code > then have ti fall back on the DB. Any ideas ? > > > > ------------------------------------------------------- > 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 > |
|
From: BrokenClock <bro...@fr...> - 2003-12-16 13:20:35
|
It seems that I forgot this stupid "reply all " button again, so I transf= er you this mail and some others. -----Message d'origine----- De : BrokenClock [mailto:bro...@fr...] Envoy=E9 : lundi 15 d=E9cembre 2003 21:37 =C0 : nw Objet : RE: PHP developpers for ErrorSystem ES-Main : "One record for one system." I never thought that ES should manage only o= ne system. I thought using name as primary key. But if you tell that's bette= r 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 langa= ge per system. Well, but I made a mistake in the design page : the deflg fie= ld 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 the yoursystem-ini table, and the default langage used by ES and all the syst= ems (but ones defined in the yoursystem-ini table) in the ES-main. And defaul= t 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 ta= ble 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 think? 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 table > 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-ErrorLevels > table) > InternalCode > (In this table i have some doubts about errorName to use by special > 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 error > 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 received > >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) instead 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 lot 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 > > > >> -----Message d'origine----- > >> De : nw [mailto:bi...@ra...] > >> Envoy=E9 : jeudi 11 d=E9cembre 2003 16:23 > >> =C0 : bro...@fr... > >> Objet : Re: PHP developpers for ErrorSystem > >> > >> > >> Hello. > >> I've read project information at project homepage and subscribed > >> error-devel mailing-list. And about Unix name, maybe you mean my > >> Sourceforge login? It's biznw. > >> I think that ErrorSystem is an interesting idea. On my mind, system > >> will be more flexible and powerfull with MySQL, but you are right > >> about synchronous development of both (db and files-driven). I > >>expect > >> from this project better knowlege of php and expierense of team > >> working. Now? you can pose a problem(s)! > >> > >> On Thu, 11 Dec 2003 15:04:56 +0100 > >> "BrokenClock" <bro...@fr...> wrote: > >> >OK, so read the home page : http://errorsystem.sourceforge.net/ > >> >Subscribe the error-devel mailing-list. > >> >Send me your Unix name (your account name on SourceForge, you must > >> >have > >> >one), so I can had you as a developper. > >> >And tell me what you think about this project, your suggestion and > >> >all. > >> > > >> >Pleased to have you with us. > >> > > >> >Stephane > >> > > >> >> -----Message d'origine----- > >> >> De : Andrew [mailto:bi...@us...] > >> >> Envoy=E9 : mardi 9 d=E9cembre 2003 15:20 > >> >> =C0 : bro...@us... > >> >> Objet : RE: PHP developpers for ErrorSystem > >> >> > >> >> > >> >> Hello! > >> >> > >> >> I have some expierence in php programming and want to learn > >> >> > >> >> more. Will be glad to share workload! > >> >> > >> > > >> > >> > > > > |
|
From: <son...@ss...> - 2003-12-15 15:59:46
|
Should we depend on MySQL to enforce empty fields ? Currently, this might be a good idea, but other databases (notably Oracle and postgreSQL) don't handle NULLs too well, so it might be better to write the checking code then have ti fall back on the DB. Any ideas ? |
|
From: <son...@ss...> - 2003-12-15 15:52:19
|
One slight problem: MySQL nor SQLite supports Foregin key. What I recommend doing is to put an LanguageID on each language in ES-language, and then have a simlar field in ES-main to link it. I'm setting up the MySQL tables now, I'll get a schema up. As for the DB layor, I'm currently doing it as a class, but at this point I can change that without much effort. > I transfer your mail to the ES-devel mailing-list so the others can share > your idears. I hope I will have more time today to answer more, and to > McTails so, but it is a big day here. On the other hand, it's going to be > a > very long day, so I *may* have some time. > > Have fun, > > Stephane > >> -----Message d'origine----- >> De : nw [mailto:bi...@ra...] >> Envoyé : lundi 15 décembre 2003 10:00 >> À : 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 table >> 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, Ðóññêèé, 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-ErrorLevels >> table) >> InternalCode >> (In this table i have some doubts about errorName to use by special >> 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 error >> 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 received >> >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) instead 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 lot 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 >> > >> >> -----Message d'origine----- >> >> De : nw [mailto:bi...@ra...] >> >> Envoyé : jeudi 11 décembre 2003 16:23 >> >> À : bro...@fr... >> >> Objet : Re: PHP developpers for ErrorSystem >> >> >> >> >> >> Hello. >> >> I've read project information at project homepage and subscribed >> >> error-devel mailing-list. And about Unix name, maybe you mean my >> >> Sourceforge login? It's biznw. >> >> I think that ErrorSystem is an interesting idea. On my mind, system >> >> will be more flexible and powerfull with MySQL, but you are right >> >> about synchronous development of both (db and files-driven). I >> >>expect >> >> from this project better knowlege of php and expierense of team >> >> working. Now? you can pose a problem(s)! >> >> >> >> On Thu, 11 Dec 2003 15:04:56 +0100 >> >> "BrokenClock" <bro...@fr...> wrote: >> >> >OK, so read the home page : http://errorsystem.sourceforge.net/ >> >> >Subscribe the error-devel mailing-list. >> >> >Send me your Unix name (your account name on SourceForge, you must >> >> >have >> >> >one), so I can had you as a developper. >> >> >And tell me what you think about this project, your suggestion and >> >> >all. >> >> > >> >> >Pleased to have you with us. >> >> > >> >> >Stephane >> >> > >> >> >> -----Message d'origine----- >> >> >> De : Andrew [mailto:bi...@us...] >> >> >> Envoyé : mardi 9 décembre 2003 15:20 >> >> >> À : bro...@us... >> >> >> Objet : RE: PHP developpers for ErrorSystem >> >> >> >> >> >> >> >> >> Hello! >> >> >> >> >> >> I have some expierence in php programming and want to learn >> >> >> >> >> >> more. Will be glad to share workload! >> >> >> >> >> > >> >> >> >> >> > >> >> > > > > ------------------------------------------------------- > 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_id78&alloc_id371&op¿ick > _______________________________________________ > ErrorSystem-devel mailing list > Err...@li... > https://lists.sourceforge.net/lists/listinfo/errorsystem-devel > |
