On 02/21/2016 02:22 PM, Kevin Waterson wrote:
> I do not understand why I am getting this error.
> I have joined the table correctly, is this not sufficient?
>
> forge=> select * FROM generate_series('2016-01-22', '2017-12-31', '1
> day'::interval) AS day
> LEFT JOIN (
>
I do not understand why I am getting this error.
I have joined the table correctly, is this not sufficient?
forge=> select * FROM generate_series('2016-01-22', '2017-12-31', '1
day'::interval) AS day
LEFT JOIN (
select *, generate_series(c.start_time,
c.end_time, '2 wee
Yep, that nailed it.
Thanks for you time and help.
--
View this message in context:
http://postgresql.nabble.com/ERROR-missing-FROM-clause-entry-for-table-tp5886750p5887183.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgs
On 2/11/2016 2:15 AM, bigkev wrote:
...
This stores the start_time, which is the date and time a series of calls
begins. The duration defines how long this event(call) will go for, and the
end_time defines when the schedule will stop.
I need to generate a calendar eg: 1 year with intervals of 1 d
The call_schedule table looks like this
id| integer | not null default
nextval('call_schedule_id_seq'::regclass)
account_id| integer | not null
user_id | integer | not null
call_type_id | integer
On 2/10/2016 1:33 AM, bigkev wrote:
Yes, c.start_time is a timestamp.
It is really late where I am, so I apologize if I'm being dense...
My goal is to list events (calls) which are scheduled on fortnightly basis.
The query works with hard coded values, but I need to generate results for
days
Yes, c.start_time is a timestamp.
My goal is to list events (calls) which are scheduled on fortnightly basis.
The query works with hard coded values, but I need to generate results for
days beginning at the start_time and ending with the end_time.: eg:
2016-02-06
2016-02-07
2016-02-08 | Some acco
On 2/9/2016 11:11 PM, bigkev wrote:
I am receiving this error for the query pasted below.
Is the LEFT JOIN on the table not enough?
What needs to happen here?
I am guess something to do with derived tables
http://pastie.org/10715876
Your error is in the reference to c.start_time, c.end_time.
Hello
> -Original Message-
> From: pgsql-general-ow...@postgresql.org
> [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of bigkev
> Sent: Mittwoch, 10. Februar 2016 08:11
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] ERROR: missing FROM-clause entry f
On Wed, Feb 10, 2016 at 4:11 PM, bigkev wrote:
> I am receiving this error for the query pasted below.
> Is the LEFT JOIN on the table not enough?
> What needs to happen here?
> I am guess something to do with derived tables
>
> http://pastie.org/10715876
Please be sure to copy the content of you
I am receiving this error for the query pasted below.
Is the LEFT JOIN on the table not enough?
What needs to happen here?
I am guess something to do with derived tables
http://pastie.org/10715876
--
View this message in context:
http://postgresql.nabble.com/ERROR-missing-FROM-clause-entry-for
On Tue, Jun 17, 2008 at 5:03 AM, m laks <[EMAIL PROTECTED]> wrote:
> --- On Tue, 6/17/08, Tommy Gildseth <[EMAIL PROTECTED]> wrote:
> 1. Where is this documented, and
> 2. where can I read more about what changed
> between the 7 series and 8 series that caused this?
http://www.postgresql.org/docs
m laks wrote:
--- On *Tue, 6/17/08, Tommy Gildseth /<[EMAIL PROTECTED]>/* wrote:
F
How about something along these lines:
delete from instancetable
USING imagelevel
WHERE (
(imagelevel.serparent= '1.2.840.113704.1.111.4640.1185891989.4') and
(instancetable.
--- On Tue, 6/17/08, Jaime Casanova <[EMAIL PROTECTED]> wrote:
maybe the add_missing_from parameter in postgresql.conf is what you
need to get some sleep :)
it's there for older application like yours
Dear Jaime,
Tommy's suggestion worked right away. I wanted to
understand more of the philiosp
--- On Tue, 6/17/08, Tommy Gildseth <[EMAIL PROTECTED]> wrote:
F
How about something along these lines:
delete from instancetable
USING imagelevel
WHERE (
(imagelevel.serparent= '1.2.840.113704.1.111.4640.1185891989.4') and
(instancetable.imageuid= imagelevel.sopinsuid)
)
Thank You so muc
m laks wrote:
Hi,
I am migrating to postgresql 8.1 from 7.4 with debian.
Now I notice that one of my perl DBI scripts is crashing with the error
above, and worked fine before.
LTA_IDB=# delete from instancetable where ( (imagelevel.serparent=
'1.2.840.113704.1.111.4640.1185891989.4') and (i
On Tue, Jun 17, 2008 at 1:25 AM, m laks <[EMAIL PROTECTED]> wrote:
> Hi,
> I am migrating to postgresql 8.1 from 7.4 with debian.
>
[...]
>
> the following worked before:
>
> LTA_IDB=# delete from instancetable where ( (imagelevel.serparent=
> '1.2.840.113704.1.111.4640.1185891989.4') and (instanc
Hi,
I am migrating to postgresql 8.1 from 7.4 with debian.
Now I notice that one of my perl DBI scripts is crashing with the error above,
and worked fine before.
>From google I learn that postgresql is getting tougher on us malfeasant
>coders who violate the SQL rules :(.
I have not slept
18 matches
Mail list logo
