If I switch the dsn back to our Postgres db and not the test sqlite db, it works, but it's the same SQL generated:
cat t/47-find_unused_number.t
#!/usr/bin/env perl
use strict;
use warnings;
use Data::Dumper;
use Test::More tests => 2;
use_ok 'API::Schema';
my $dsn = "dbi:Pg:dbname=api;host=127.0.0.1;port=5432";
my $apidb = API::Schema->connect( $dsn, 'postgres' );
my $ddi_available = $apidb->resultset('CompleteNumberE164View')->find(
{
ddi => 441224900999,
is_used => 0
}
);
note 'DDI found: ' . $ddi_available->ddi;
ok( $ddi_available->ddi eq '441224900999', 'Found available DDI.' );
prove -l t/47-find_unused_number.t
t/47-find_unused_number.t .. ok
All tests successful.
Files=1, Tests=2, 1 wallclock secs ( 0.02 usr 0.00 sys + 0.55 cusr
+ 0.06 csys = 0.63 CPU)
Result: PASS
The original schema was generated for Postgres, but populated via our sql fixtures for sqlite. The search goes work, so must be DBIx::Class related?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|