Home Page Instructions Don't Work

[GoogleCodeExporter]

When I launch FINally.py, a database is created, but it has the name
SQLiteExpenses.db.  The instructions don't mention this.  

Running SQLiteDrivers.py does not seem to create a new database at all.

Original issue reported on code.google.com by matt.van...@gmail.com on 27 Jan 2008 at 3:56

[GoogleCodeExporter]

WHAT?!?

Are you sure:

1) you are launching FINally.py without a command line argument? 
2) that the database it creates is not called FINally_data.db?

Regardless, this functionality has been re-worked on the fileCheck branch, and 
when
this is checked into the trunk it should behave correctly. However, this is a 
good
reminder to update the instructions when the branch is merged.

Original comment by Daniel.S...@gmail.com on 27 Jan 2008 at 2:06

[GoogleCodeExporter]

Original comment by Daniel.S...@gmail.com on 27 Jan 2008 at 2:06

• Changed state: Assigned

[GoogleCodeExporter]

I used the branch fileCheckDev.

I opened a command line and typed "python FINally.py".
The automaticaly created a database for me called "SQLiteExpenses.db".

I deleted all of the *.pyc files and the database.
I typed "python SQLiteCommands.py".
No error messages, but nothing apparent happened.  I have scanned my hard drive 
for
*.db files and don't see one.

When I then type "python FINally.py", I get the same results as before.  
Namely, the
database SQLiteExpenses.db is created.

So, this behavior does not match the instructions on the home page.

Original comment by matt.van...@gmail.com on 27 Jan 2008 at 5:35

[GoogleCodeExporter]

Ahhh... I was unaware that you were using the branch, I was searching the trunk 
for
instances of SQLiteExpenses.db and couldn't find any. I will take a look at 
this and
make sure the documentation matches the functionality.

Original comment by Daniel.S...@gmail.com on 27 Jan 2008 at 6:29

[GoogleCodeExporter]

ok, a few things on this issue...

1) I refactored the SQLite functionality into two files: SQLiteCommand and 
dbDrivers. SQLiteCommands contains a bunch of strings that represent SQLite 
commands 
and no functionality. dbDrivers contains all of the SQLite driver functions. SO 
- 
you probably wanted to execute dbDrivers.py instead of SQLiteCommands.py. 

2) Fin-ally startup functionality has now been modified to center around 
FINally.py -
 meaning you should always execute FINally.py (even if no database exists)

3) I didn't expect you and Tim to be so intent on checking out my branch - so I 
was 
making changes sans documentation. This will be resolved with my merge back to 
the 
trunk today :)

Original comment by Daniel.S...@gmail.com on 27 Jan 2008 at 10:02

[GoogleCodeExporter]

ok, home page instructions have been updated. Now, the only thing that needs to 
be 
done at startup is to launch FINally.py! woot.

Original comment by Daniel.S...@gmail.com on 27 Jan 2008 at 10:33

• Changed state: Pending

[GoogleCodeExporter]

Looks like that fixed it.  Shall I leave it to you to close this issue?

Original comment by matt.van...@gmail.com on 27 Jan 2008 at 11:04

[GoogleCodeExporter]

Original comment by Daniel.S...@gmail.com on 3 Feb 2008 at 9:12

• Changed state: Closed