On Dec 8, 1:24 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: > Any reason to not use both 1 and 2 if hdd space permits?
Think of them as 2 separate activities, addresssing 2 very different needs / outcomes: [1] Database native backup: provides dependable recovery path for _this_ deployment (or any w/ this db backend), or any place where a compatible version of this backend / server is available (e.g. portable accross machines, but not backends). [2] csv data backup: provides portable data backup, easily accessible and manipulatable - e.g. can import into other backends, can manipulate with spreadsheets, python, etc. easily. Note: May (or may not) provide a complete one step recovery step for a running system. Then choose appropriately. Note: if you have [1] and _that_ db server available somewhere, then you can always create [2] from it. If [1] is a proprietary server, and license may not be portably available, then [2] starts to look like it has more utility. - Yarko > > -Thadeus > > > > On Mon, Dec 7, 2009 at 8:23 PM, villas <villa...@gmail.com> wrote: > > Indeed, take Firebird for example, I would only ever choose to back up > > using the official utility which backs up all data, stored procedures, > > generators (for autoinc), does garbage collection etc and produces a > > clean 'transportable' backup which can be restored on any platform. > > Sqlite users might appreciate something built in though. > > > IMO even more useful would be a simple replication feature - I think > > that would be a great selling point! > > David > > > -- > > > You received this message because you are subscribed to the Google Groups > > "web2py-users" group. > > To post to this group, send email to web...@googlegroups.com. > > To unsubscribe from this group, send email to > > web2py+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/web2py?hl=en. -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
