Re: ERROR: invalid input syntax for integer: ""
От | Tom Lane |
---|---|
Тема | Re: ERROR: invalid input syntax for integer: "" |
Дата | |
Msg-id | 6654.1285258482@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | ERROR: invalid input syntax for integer: "" (kevin burdish <bigswifty00000@gmail.com>) |
Список | pgsql-novice |
kevin burdish <bigswifty00000@gmail.com> writes: > ERROR: invalid input syntax for integer: "" > [from] > select l.logid,date_trunc('second',logtime) AS > date,l.detail,l.status,l.logtype,l.assetid, e.parententityid,e.address > from pxlog l -- , pxentity e > LEFT OUTER JOIN pxentity e ON ( l.assetid::BIGINT ) = e.entityid > where l.logid >= 99999 > -- AND l.assetid != '' > order by l.logid > limit 10; Apparently you're trying to cast some empty-string value(s) of l.assetid to bigint. Even if the test for that weren't commented out :-(, you can't really assume that it will be applied before the cast is done. You could possibly make this work without errors by doing left join on CASE WHEN l.assetid != '' THEN l.assetid::BIGINT = e.entityid ELSE false END but don't be surprised if the performance is horrid. On the whole I'd strongly suggest rethinking your data representation; the reason this is giving you trouble is you made a bad choice of how to represent l.assetid. Perhaps it'd work better if it were a bigint column in the first place. It's not clear exactly what you intend the empty-string entries to mean, but if they mean "unknown" then it'd be better to use NULL for them. regards, tom lane
В списке pgsql-novice по дате отправления: