Bug #86702 for DBIx-VersionedDDL: Bug in _get_current

Thu Jul 04 07:34:26 2013 JIRA [...] cpan.org - Ticket created

Subject:

Bug in _get_current_version

Hello,

line 336: my $sql = q{select version from schema_version};
should be changed to
my $sql = q{select max(version) from schema_version};

Right now it returns the lowest number in the version column (at least on postgres).

Thu Jul 04 17:09:26 2013 dhorne [...] cpan.org - Correspondence added

Hi I'm not really familiar with Postgres, but with most DBs I use, unless you provide an order by clause, you don't know what order the rows will appear in. However, I'm concerned that you have two numbers in your schema's version table. There should only ever be one - the version that the schema is at. Can you tell me how you ended up with two versions? I'd need to replicate that scenario to prevent it from happening On Thu Jul 04 07:34:26 2013, JIRA wrote: Show quoted text

> Hello, > > line 336: my $sql = q{select version from schema_version}; > should be changed to > my $sql = q{select max(version) from schema_version}; > > Right now it returns the lowest number in the version column (at least on > postgres).

Thu Jul 04 17:09:26 2013 The RT System itself - Status changed from 'new' to 'open'

Sat Jul 06 05:29:41 2013 JIRA [...] cpan.org - Correspondence added

On 2013-07-04 17:09:26, DHORNE wrote:

Show quoted text

> However, I'm concerned that you have two numbers in your schema's
> version table. There should only ever be one - the version that the
> schema is at.

Yes I had a row for every version lower than current one. I was maintaining the table manually for some time.
No bug then.

Sun Jul 07 07:15:26 2013 JIRA [...] cpan.org - Status changed from 'open' to 'resolved'

Bug #86702 for DBIx-VersionedDDL: Bug in _get_current_version