handle aliasing of STORE'd attributes for looking up into read_only attribute list ...
pod text/link was reversed in a few cases

$ perldoc perlpod

To control what text is used for display, you use ""L<text|...>"", as in:

*   "L<text|name>"

    Link this text to that manual page. E.g., "L<Perl Error
    Messages|perldiag>"

*   "L<text|name/"sec">" or "L<text|name/sec>"

    Link this text to that section in that manual page. E.g.,
    "L<postfix "if"|perlsyn/"Statement Modifiers">"

*   "L<text|/"sec">" or "L<text|/sec>" or "L<text|"sec">"

    Link this text to that section in this manual page. E.g., "L<the
    various attributes|/"Member Data">"
prep 1.626 release
Fixed skip() count arg in t/48dbi_dbd_sqlengine.t
remove git-svn-vsn.pl utility that's no longer needed
Fixed VERSION regression in DBI::SQL::Nano

Looks like the previous change "Apply the git-svn-vsn.pl script to "fix"
the svn keywords like Id and Revision" wasn't done quite right.
The VERSION is fixed now we're no longer using svn.
I've just bumped the number.
Prep 1.627 release
typo fixes

a little intuition used in some changes so please double check
Merge pull request #1 from dsteinbrunner/master

typo fixes
Change DBI's docs from svn to git

Note that the Roadmap has moved to Old and is thus not
supposed to be available.

I /think/ that "Director (CTO) of Ingeneering" should be
"Director (CTO) of Engeneering"
Tweak reference to Ingeneering and remove (broken) url
    Always insert *ALL* fields on INSERT

    table foo (
        c_foo  integer,
        foo    char (2)
        );

    insert into foo (c_foo) values (1);

    resulted in passing *only* c_foo. When using CSV, that resulted in

    c_foo,foo
    1

    instead of

    c_foo,foo
    1,

    note the trailing ,
Always insert *ALL* fields on INSERT in Nano
Hardcoded version strings

Now that $Revision$ is useless in git, use hardcoded $VERSION strings,
which are easier to update.

Removed trailing whitespace from touched files
Clarify bind_col TYPE attribute is sticky
Support multiple folders in DBD::File's f_dir attribute

No tests yet and a few locations where things still will go wrong
when the catdir () is involved
Use a new attribute: f_dir_ext

Extended dir search now more explicit. One of the reasons not to use
a ref in f_dir is that the current definition is (very) clear and we
should not break that. What e.g. would we use to write new files?

If a table is opened from folder 2, then deleted and recreated, does
that mean we should re-use folder 2? If f_dir working as before this
problem disappears
Jens really prefers f_dir_search over f_dir_ext
Make deep searches work.

Tested with DBD::CSV, now all we need is sanity checks and agreement on
this new feature
Spelling fixes.

Signed-off-by: H.Merijn Brand - Tux <h.m.brand@xs4all.nl>