Don't use special chars in timestamps

[GoogleCodeExporter]

atm flyback creates "%Y-%m-%d %H:%M:%S" directories to store the data in there.
this works on ext3 and other *nix filesystems, which allow a wide set of
characters in names, but fails on ntfs/fat32/othernonsogoodfs :)

This structure should be either completely user-editable (the user would
have to input a string strptime() accepts, or at least have some options like:
"%Y-%m-%d %H:%M:%S"
"%Y%m%d%H%M%S"
"%U" (yeah, there ARE ppl loving unix timestamps :>)

Original issue reported on code.google.com by zhen...@gmail.com on 9 Nov 2007 at 12:52

[GoogleCodeExporter]

i don't want to make it user editable, less people swap it around and migrating 
one
to the other gets to be a pain.  but 20010101010101 is not very easy-on-the 
eyes....

how about "2001-01-01__01.01.01.backup"?

Original comment by pub...@kered.org on 9 Nov 2007 at 2:21

[GoogleCodeExporter]

or "2001-01-01_01-01-01.backup" - yeah that would be possible (and would be 
okay for
me :))

for the user-editable idea:
you don't want it, as you will need a more intelligent/complex mechanism to 
detect
backup dirs, right?
what about of adding a file ".flybackup" or so to each dir, with some metadata 
in it
(like timestamp in an unified format etc) and then scan for dirs with such a 
file in
them? then you could let the user break everything about the naming scheme, but 
still
have a working flyback :)

Original comment by zhen...@gmail.com on 9 Nov 2007 at 8:00

[GoogleCodeExporter]

Maybe put the metadata/marker in the flyback directory along side the backup
directory, rather than in the backup directory, and with essentially the same 
name.

e.g. if the backup is in flyback/2001-01-01_01_01_01.backup then the metadata 
would
be in flyback/2001-01-01_01_01_01.info 

Original comment by staz6...@gmail.com on 9 Nov 2007 at 10:32

[GoogleCodeExporter]

there is quite a bit of metadata i want to store eventually, (i plan to put it 
all
into a sqlite3 file)  i'll add this when i implement the rest.

but to solve the immediate problem, i've changed the backup dir date format.  
but i
didn't write a migration function, so you might just want to delete all your 
backups
and start over.  (or you can rename them manually if you want)

Original comment by pub...@kered.org on 10 Nov 2007 at 1:53

• Changed state: Fixed