Thats fine! You've been a wonderful help. One last question, does it "look" like it should be working properly? I will go through the link you sent and talk to IT again. But again, I do appreciate your help.
Here is the Controller calling up Zips:
package WeilMclain::Controller::ContractorLocator;
use strict;
use warnings;
use base 'Catalyst::Controller';
=head1 NAME
WeilMclain::Controller::ContractorLocator - Catalyst Controller
=head1 DESCRIPTION
Catalyst Controller.
=head1 METHODS
=cut...
Oh yes. those are the "zips_backup". I forgot they were referenced in the above "add columns"
The complete list is:
zip_code
zip_type
city_name
city_type
state_name
state_abbr
latitude
longitude
Oh really? I thought that was the only bit correct.
The columns in the "zips_backup" table are:
zip_code
city_name
state_name
state_abbr
latitude
longitude
Thanks Steve!
Here is the bit of code I think is incorrect
sub get_zip {
my ($self, $city, $state) = @_;
#return undef unless ($city && $state =~ /^(\d*)$/);
if (my $zip = $self->single({city_name => uc($city),state_abbr=>uc($state)},{columns => [qw/zip_code/]})) {
return...
No, I wrote it correctly. It reads: "zips" became corrupt so I changed the perl script to pull from "zips_backup". We had a backup table of "zips" called "zips_backup" in case we ever lost our zip code information.
Now, my saying corrupt was the wrong term to use. When numeric was changed to...
Hope someone is familiar with this.
Server: Apache
Database: Postgre SQL
Issue with zips. In my postgresql I had two tables one titled "zips" and the other "zips_backup". "zips" became corrupt so I changed the perl script to pull from "zips_backup". The locator works great when searching by...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.