Hmm weird problem with SELECT

n00854180t

Hey all, haven't been around lately.

Anyway, I have a problem with my cart script. I have 2 tables that contain shipping rates. Now, these tables only account for weights up to 128. So what I was doing was checking if the number to be used in my query is > 128 and then set that number back to 128 if it is. However, for some reason whenever I try to select from this table with any increment greater than 80 it just gives me an error(the increments are 96, 112, and 128).

I get this error from pg_last_error() : ERROR: parser: parse error at or near "," at character 55

Here is some code:

<?php

...

$priquery = "SELECT cost from us_prioritymail WHERE weight = $priorlookup";
$priorresult = pg_query($priquery) or die(pg_last_error()); 

...

?>

LordShryku

What's the value of $priorlookup? Echo $priquery to the screen and post it back. Somehow you have a comma in it as far as it thinks

n00854180t

When I echo it it says it is 96 or whatever the number is. I will try it with a constant value and see what the result is.

n00854180t

Hmm, it is still giving me the same error, even though I replaced $priorlookup with 96 (as soon as I get up to where priorlookup is 96 or greater it gives me the error).

LordShryku

Strange...

echo the query to the screen....

n00854180t

Hmm I had to use a session var to get it to echo, but it echoes a normal query (SELECT rate FROM us_prioritymail WHERE weight = 96).

LordShryku

<?php

...

$priquery = "SELECT cost from us_prioritymail WHERE weight = $priorlookup";
echo $priquery;
die(); // don't execute it
$priorresult = pg_query($priquery) or die(pg_last_error()); 

...

?>

n00854180t

^ Edit sorry heh.

n00854180t

select cost from us_prioritymail where weight = priorl,ookup;

I had to put that in to recreate that same error.

n00854180t

Very strange behavior here. I put a if x >= 80 in there to set priorlookup to 96 and it selected the correct value from the db, but when the weight var got up to the point where priorlookup would actually have been 96 it gave me the error (priorlookup is a rounded number based on totalweight).

n00854180t

Bump

parawizard

hmmmm maybe you should post all your code?

that would help me trying to find the problem 🙂

anywaz maybe the problem is the database field type ? it is storing it with other characters or something?

n00854180t

Hmm that could very well be the problem. The cost field is of type VarChar. I will try changing it to a number type. I don't really want to post the entire script because it is long and fairly sloppy. But if you don't really mind that, I will post a text version on my webhost. First I will test that field change.

n00854180t

Alright, well I made the field change, but I am still getting the same error. I have noticed that it only happens when the $totalWeight var is 84 or above. The reason that is strange is that it rounds it off to the next increment of 16 before selecting from the table. Which means that at 81 it will round to 96 and select the correct value without the error, but at 84 (the weight goes by 3) it gives me the error (and the query is still selecting by using the 96 value).

n00854180t

Any ideas parawizard, LordShryku?

n00854180t

Bleh...still stumped about this problem. Sigh bump...

parawizard

i have pmed you.......check your pms