jspdbadmin-cvs Mailing List for JSPDBAdmin
Status: Planning
Brought to you by:
aalmenar
Menu
▾
▴
jspdbadmin-cvs — CVS CHANGES LIST
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
|
|---|
|
From: Adrian A. <aal...@us...> - 2002-09-03 02:11:07
|
Update of /cvsroot/jspdbadmin/CVSROOT In directory usw-pr-cvs1:/tmp/cvs-serv16624 Modified Files: syncmail Log Message: Little Changes Index: syncmail =================================================================== RCS file: /cvsroot/jspdbadmin/CVSROOT/syncmail,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- syncmail 3 Sep 2002 01:01:48 -0000 1.2 +++ syncmail 3 Sep 2002 02:11:04 -0000 1.3 @@ -68,7 +68,7 @@ import getopt # Notification command -MAILCMD = '/bin/mail -s "CVS: %(SUBJECT)s" %(PEOPLE)s 2>&1 > /dev/null' +MAILCMD = '/bin/mail -s "cvs commit: %(SUBJECT)s" %(PEOPLE)s 2>&1 > /dev/null' # Diff trimming stuff DIFF_HEAD_LINES = 20 |
|
From: Adrian A. <aal...@us...> - 2002-09-03 01:03:31
|
Update of /cvsroot/jspdbadmin/jspdbadmin In directory usw-pr-cvs1:/tmp/cvs-serv1742 Modified Files: LICENSE Log Message: Fixing CVS Index: LICENSE =================================================================== RCS file: /cvsroot/jspdbadmin/jspdbadmin/LICENSE,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- LICENSE 30 Jul 2002 05:12:13 -0000 1.2 +++ LICENSE 3 Sep 2002 01:03:28 -0000 1.3 @@ -2,7 +2,8 @@ Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. - 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. |
|
From: Adrian A. <aal...@us...> - 2002-09-03 01:01:51
|
Update of /cvsroot/jspdbadmin/CVSROOT
In directory usw-pr-cvs1:/tmp/cvs-serv1308
Modified Files:
syncmail
Log Message:
Index: syncmail
===================================================================
RCS file: /cvsroot/jspdbadmin/CVSROOT/syncmail,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** syncmail 30 Jul 2002 04:24:58 -0000 1.1
--- syncmail 3 Sep 2002 01:01:48 -0000 1.2
***************
*** 113,117 ****
# lock contention. What a crock.
if contextlines > 0:
! difftype = "-C " + str(contextlines)
else:
difftype = "-u"
--- 113,117 ----
# lock contention. What a crock.
if contextlines > 0:
! difftype = "-u"
else:
difftype = "-u"
|
|
From: Adrian A. <aal...@us...> - 2002-09-02 23:50:57
|
Update of /cvsroot/jspdbadmin/jspdbadmin In directory usw-pr-cvs1:/tmp/cvs-serv19206 Modified Files: JSPDBADMIN-PROPOSAL.txt Log Message: Some cosmetic changes to the proposal Index: JSPDBADMIN-PROPOSAL.txt =================================================================== RCS file: /cvsroot/jspdbadmin/jspdbadmin/JSPDBADMIN-PROPOSAL.txt,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** JSPDBADMIN-PROPOSAL.txt 2 Sep 2002 23:34:40 -0000 1.1 --- JSPDBADMIN-PROPOSAL.txt 2 Sep 2002 23:50:53 -0000 1.2 *************** *** 1,4 **** ! Proposal for JSPDBAdmin ! ======================= --- 1,4 ---- ! Proposal for JSPDBAdmin 1.0 ! =========================== *************** *** 11,28 **** - Create an API that can handle at least for starting ORACLE, MySQL Databases. - Provide maximum modularity in the API ! - - Make the core of the API just handling the most similar features of each DB.- Make a web interface that uses this API. - - This web interface must have i18n features. - - This web interface also have to cover all databases. - If we need to rely on a Servlet API we must use 2.3 for now ! - Also the servlet-container to use is the reference implementation for this Servlet API Tomcat 4.1.x ! Things TO DO: ! ============ ! - Select the build tool we are going to use. (Jakarta-ant is the best proposed).- Select Logging, Database Pool, Taglibs we probably are going to need. ! Later: ! ===== ! - After we have the core, then make extensions to every database specific ! features like DB File size, % of data occupied, and things like that. --- 11,32 ---- - Create an API that can handle at least for starting ORACLE, MySQL Databases. - Provide maximum modularity in the API ! - - Make the core of the API just handling the most similar features of each DB. ! - Make a web interface that uses this API. - - This web interface must have i18n features. - - This web interface also have to cover all databases. - If we need to rely on a Servlet API we must use 2.3 for now ! - Also the servlet-container to use is the reference implementation for this Servlet ! API Tomcat 4.1.x ! Things TODO: ! =========== ! - Select the build tool we are going to use. (Jakarta-ant is the best proposed). ! - Select Logging, Database Pool, Taglibs we probably are going to need. ! ! TODO Later: ! ========== ! - After we have the core, then make extensions to every database specific features ! like DB File size, % of data occupied, and things like that. |
|
From: Adrian A. <aal...@us...> - 2002-09-02 23:34:43
|
Update of /cvsroot/jspdbadmin/jspdbadmin
In directory usw-pr-cvs1:/tmp/cvs-serv16048
Added Files:
JSPDBADMIN-PROPOSAL.txt
Log Message:
First Draft Proposal Subject to change of JSPDBAdmin
--- NEW FILE: JSPDBADMIN-PROPOSAL.txt ---
Proposal for JSPDBAdmin
=======================
This document is a proposal for JSPDBAdmin Software.
Major Goals:
===========
The major goals for JSPDBAdmin 1.0 are to:
- Create an API that can handle at least for starting ORACLE, MySQL Databases.
- Provide maximum modularity in the API
- - Make the core of the API just handling the most similar features of each DB.- Make a web interface that uses this API.
- - This web interface must have i18n features.
- - This web interface also have to cover all databases.
- If we need to rely on a Servlet API we must use 2.3 for now
- Also the servlet-container to use is the reference implementation for this Servlet API Tomcat 4.1.x
Things TO DO:
============
- Select the build tool we are going to use. (Jakarta-ant is the best proposed).- Select Logging, Database Pool, Taglibs we probably are going to need.
Later:
=====
- After we have the core, then make extensions to every database specific
features like DB File size, % of data occupied, and things like that.
|
