evilny0/fpdb
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
2,140 Commits 1 Branch 0 Tags
6d54da1c49b1f1ed4f96130b355642d0b52603de
Commit Graph
33 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
fpdb-mme 6d54da1c49 Merge branch 'master' of git://git.assembla.com/fpdboz 
Conflicts:
	pyfpdb/Configuration.py
	pyfpdb/SQL.py

note:hopefully got the merge right
 2009-11-04 18:34:28 +01:00
fpdb-mme 9063d9749c removed all occurences of db_type/db-type 2009-11-03 19:18:51 +01:00
fpdb-mme 92f98e9f51 added an application wide exception handler 2009-11-03 16:09:58 +01:00
fpdb-mme 944d48d7ef refactored logging setup 
removed fallback to '/usr/share/python-fpdb/logging.conf' if
'logging.conf' could not be found in the current directory.
1. this looked redundant, 2. usually only root has write access
to /usr/share/*

ok or not?
 2009-11-03 15:35:20 +01:00
fpdb-mme 50bafadcb1 we throw an exception now if the user supplies an unsupported database backend 
note: checked all refences. i think we can raise savely without breaking stuff. it is only
used in Database.py on get_backend_name(), raising an exception anyways if the backend
is unknown
 2009-11-03 15:17:48 +01:00
fpdb-mme 62c915928d - added a global const to config to point to "database" directory 
- adjusted fpdb_db.py to make use use of this const
 2009-11-03 10:50:13 +01:00
fpdb-mme a18091161a added a note and some thoughts for review 2009-11-02 10:29:10 +01:00
fpdb-mme 9e94f44fa7 started defining some application wide consts. these consts (more to come 
if my approach is accepted) are used all over the fpdb and should always be
taken from one place
 2009-11-02 10:06:54 +01:00
fpdb-mme 34bbc45cb8 whitespace 2009-11-02 09:55:08 +01:00
fpdb-mme fb76540df6 added a TODO: 
if the user may passes '' (empty string) as database name via command line, his choice is ignored
when we parse the xml we allow for ''. there has to be a decission if to allow '' or not
 2009-11-02 09:54:16 +01:00
fpdb-mme d3eeeef2e8 fpdb can not handle the case where no database is defined in xml, so throw a ValueError for now 2009-11-02 09:45:53 +01:00
fpdb-mme 612d6607a1 fix: FpdbError is not defined, use ValueError instead 2009-11-02 09:40:16 +01:00
fpdb-mme 3a7d159d52 sorry, whitespace was messed up, have to find a better way to convert 2009-11-02 09:38:27 +01:00
fpdb-mme 8f2a2c20cc tried my best to write a clearer comment + simplified finding out of what the selected database is 2009-11-02 09:29:58 +01:00
fpdb-mme cb16dde365 typo 2009-11-02 09:16:18 +01:00
fpdb-mme 10343c0ef4 fixed Database.db_selected attribute. it was always be boolean True if the attribute was not set in the <database> tag 
+ it is more readable using keyword arguments explicitely
 2009-11-02 09:14:57 +01:00
fpdb-mme 75b8c4943a rewrote fix_tf() helper function to string_to_bool(). this represents better is what it actually does. 
comments stated that the function was some kind of fix for xml.dom, but XML is unaware
of python types by intention ;-)
 2009-11-02 09:09:23 +01:00
fpdb-mme d59f1eb720 added a comment what Config.supported_databases holds for readability 2009-11-02 08:52:46 +01:00
fpdb-mme d9a120a2c6 removed superfluous try ..except clause. Database.__init__() was not doing any sanity checks, 
so the try ..except clause was only covering exceptions we are actually interested in
 2009-11-02 08:48:07 +01:00
fpdb-mme 01b56919ca we take all <database> tags from xml instead of taking all <database> tags contained in <supported_databases> 
added a note on this
 2009-11-02 08:40:34 +01:00
fpdb-mme 62ee67c071 under certain circumstances attribute Config.db_selected could end up being undefined. 
this could cause later code relying on it failing in strange ways.
 2009-11-02 08:30:24 +01:00
fpdb-mme 0225987826 added basic support to add databases present in *.xml to our manager 
notes:
- i dont do too much error checking on input, guess this should be done in Configuration.py
 2009-11-01 20:07:41 +01:00
fpdb-mme f5d2f5a2dc fix: according to doctests os_independend_kill() is supposed to return None 2009-11-01 09:58:14 +01:00
fpdb-mme 6fcf81e566 bugfix: InterProcessLock.locked() was broken cause InterProcessLock.aquire() no longer raises SingleInstanceError 
- fixed InterProcessLock.locked()
- fixed doctests

notes:

- doctests run ok on linux with InterProcessLockFcntl and InterprocessLockSocket
- doctests fail on linux/wine with InterprocessLockWin32 when trying to aquire the lock held by the process created on the fly.
   just a guess ..maybe the mutex is not released automatically when terminating the process. does native win32 guarantee
   this?
 2009-11-01 09:51:00 +01:00
fpdb-mme bcbafc160d millions of changes, highlights: 
- started validating user input on create/add database
- implemented fuctionality to create sqlite databases
- never worked with sqlite,, you can not create multiple dbs in one file, so removed db attr again
- a nice todo list

Signed-off-by: fpdb-mme <jUrner@arcor.de>
 2009-11-01 07:36:18 +01:00
fpdb-mme 2ae58f8947 databases can now be activated by user 
++ refactoring

Signed-off-by: fpdb-mme <jUrner@arcor.de>
 2009-10-31 12:12:17 +01:00
fpdb-mme 604395b868 bit of refactoring + sqlite needs database too 
Signed-off-by: fpdb-mme <jUrner@arcor.de>
 2009-10-30 16:48:51 +01:00
fpdb-mme a3a72712ac again, many many changes + still ugly code 
Signed-off-by: fpdb-mme <jUrner@arcor.de>
 2009-10-30 14:23:27 +01:00
fpdb-mme 2a878d0a83 many changes 
Signed-off-by: fpdb-mme <jUrner@arcor.de>
 2009-10-29 19:32:41 +01:00
fpdb-mme e732b74956 too many changes to remember 
Signed-off-by: fpdb-mme <jUrner@arcor.de>
 2009-10-27 11:04:24 +01:00
fpdb-mme 30103c5cb2 second try... 
Signed-off-by: fpdb-mme <jUrner@arcor.de>
 2009-10-27 09:01:06 +01:00
fpdb-mme 1efdd7fc68 add DatabaseManager 2009-10-25 10:22:06 +01:00
fpdb-mme 0b0312d1ee Signed-off-by: fpdb-mme <jUrner@arcor.de> 
initial commit
 2009-10-25 00:13:35 +02:00