On Sun, May 13, 2012 at 8:11 PM, Tom Lane wrote:
> It strikes me that "cannot be cast" is a poor choice of words here,
> since the types *can* be cast if you try. Would it be better if the
> message said "cannot be cast implicitly to type foo"? We could also
> consider a HINT mentioning use of
Having all the dblink destinations on the same server makes it a much more
viable option since the chances of the dblink update failing are greatly
reduced. That said, here's a run down on the queue system I described with
some specificity toward your situation.
You can add a flag to each custome
Carlos Mennens writes:
> I'm not understanding why I'm not able to change this column type from
> char to integer?
> forza=# ALTER TABLE customers
> ALTER COLUMN cust_id TYPE integer;
> ERROR: column "cust_id" cannot be cast to type integer
Try "ALTER ... cust_id TYPE integer USING cust_id::int
On Fri, May 11, 2012 at 4:42 PM, Viktor Bojović
wrote:
> you can convert from type to type using ::varchar or ::char(size) or
> ::integer
> so you can use sequence but you will have to convert it's result to suitable
> type (that can also be put in default value of user_id attribute)
I'm not unde
All on the same cluster (only one server). Although, it would be nice to
have only one table there are real business reasons to dup the databases.
I am interested in how you dealt with a queue table. Would you take a little
time to describe the way it worked.
Johnf
On Saturday, May 12, 2012
