On 01/29/2014 02:01 PM, Tom Lane wrote:
> Craig Ringer writes:
>> I just want us to allow, by default, implicit casts FROM text (not TO
>> text) using the input function for all PostgreSQL's validated
>> non-standard types (and XML due to limited deployment of SQL/XML support
>> in client drivers)
Tom Lane-2 wrote
> Craig Ringer <
> craig@
> > writes:
>> I just want us to allow, by default, implicit casts FROM text (not TO
>> text) using the input function for all PostgreSQL's validated
>> non-standard types (and XML due to limited deployment of SQL/XML support
>> in client drivers).
>
>
Craig Ringer writes:
> I just want us to allow, by default, implicit casts FROM text (not TO
> text) using the input function for all PostgreSQL's validated
> non-standard types (and XML due to limited deployment of SQL/XML support
> in client drivers).
Sorry, that is *just* as dangerous as impli
Mike Christensen writes:
> Oh. The CREATE CAST command. Wow, I was totally unaware of this entire
> feature!
Before you get too excited about inserting your own implicit casts,
you really should get familiar with the reasons there aren't ones
already ;-).
As was mentioned upthread, we used to
On 01/29/2014 05:20 AM, Tom Lane wrote:
> John R Pierce writes:
>> On 1/28/2014 12:11 PM, Merlin Göttlinger wrote:
>>> I don't know if this is just a beginner problem but at least in my
>>> opinion it is rather complicated to use the postgres specific types
>>> and features from JDBC and its wra
As a note, the following also works:
CREATE TYPE foo AS (bar text, baz int);
CREATE TABLE table_of_foo OF foo (primary key(bar));
The one thing that doesn't work is the REF syntax and the operators that go
along with that. However, you could come up with dereferencing functions
and operators one
Thanks
On 27 Jan 2014 22:35, "Bhushan Pathak" wrote:
>
> Hello,
>
> We have recently shifted to postgresql version 9.2.4 from 9.1.3. After
the migration, we observed that some of our delete queries on single table
[which have triggers, which in turn call other functions] have started
consuming lar
On Tue, Jan 28, 2014 at 03:38:49PM -0800, Mike Christensen wrote:
> Oh. The CREATE CAST command. Wow, I was totally unaware of this entire
> feature!
See, this is why Postgres really is better than you ever think. Just
when you're convinced that you have a totally impossible problem, it
turns o
Oh. The CREATE CAST command. Wow, I was totally unaware of this entire
feature!
On Tue, Jan 28, 2014 at 3:36 PM, Mike Christensen wrote:
> How do you create casts in Postgres?
>
>
> On Tue, Jan 28, 2014 at 3:24 PM, Andrew Sullivan wrote:
>
>> On Tue, Jan 28, 2014 at 02:55:03PM -0800, Mike Chri
How do you create casts in Postgres?
On Tue, Jan 28, 2014 at 3:24 PM, Andrew Sullivan wrote:
> On Tue, Jan 28, 2014 at 02:55:03PM -0800, Mike Christensen wrote:
>
> > I'd be curious as to what types of bugs were caused by these implicit
> > casts..
>
> Typically, they were cases when there was a
On Tue, Jan 28, 2014 at 02:55:03PM -0800, Mike Christensen wrote:
> I'd be curious as to what types of bugs were caused by these implicit
> casts..
Typically, they were cases when there was an ambiguity that the
programmer didn't understand, causing applications to blow up in
surprising and wonde
Interesting!
I'd be curious as to what types of bugs were caused by these implicit
casts..
Note 8.3 was in the days back before ORMs became popular, so "just write
better SQL" was a perfectly decent solution to the problem back then. Now
days, this requirement might make Postgres incompatible wi
On 1/28/2014 2:35 PM, Mike Christensen wrote:
This works. However, to agree with the original poster's point, if
Postgres could be a little more forgiving about values that could be
interpreted as correct (like an implicit cast between numeric and enum
and string and enum) then we wouldn't hav
I've had the same problem as well with NHibernate (On .NET) with Postgres
ENUM types. Luckily, NHibernate is incredibly powerful and you *can* get
everything working flawlessly, however it takes some serious digging into
the source code and reading the docs to figure it out. The main issue is
tha
On 1/28/2014 1:20 PM, Tom Lane wrote:
I think you can fix it by explicitly casting your placeholders, eg
"?::macaddr".
that might work for a wrapper that lets you roll your own SQL, but I
thought he said one of these autogenerated SQL, taking it out of his
control.
--
john r pierce
Hi all,
I have completed all the planned changes for the version 1.0.1 and
merged them to the v1.0testing branch. Anyone interested in testing is
very welcome. You can report bugs (hope there wont be any) and make
notes either directly to my email gray...@gmail.com or on GiHub's
Issue page https:/
John R Pierce writes:
> On 1/28/2014 12:11 PM, Merlin Göttlinger wrote:
>> I don't know if this is just a beginner problem but at least in my
>> opinion it is rather complicated to use the postgres specific types
>> and features from JDBC and its wrappers.
> these issues are entirely created by
On 1/28/2014 12:11 PM, Merlin Göttlinger wrote:
I don't know if this is just a beginner problem but at least in my
opinion it is rather complicated to use the postgres specific types
and features from JDBC and its wrappers.
these issues are entirely created by the wrappers you're using. like
Hello fellow postgres users,
I am very new to postgres and databases in general. I needed a database for
a project and I chose to use PostgreSQL. I googled around until I was
confident enough to do the things I wanted to do.
I have written two applications that both use the same database.
The fi
antono124 wrote:
> Lets say that we have 2 tables.
> Create Table "table1" Of "type1"
> Create Table "table2" Of "type2"
>
> I want to refer the first table in the second. I want to
> reference the whole table not only one field, so something like
> that:
>
> CREATE TYPE type2 AS OBJECT (
> va
It turns out IT screwed something up when they installed 9.2. The actual
server/client running is still pointing to 8.4.
Thanks, guys.
Susan
On Mon, Jan 27, 2014 at 4:48 PM, Tom Lane wrote:
> Susan Cassidy writes:
> > This is 9.2
>
> I'd bet a very good dinner that it isn't --- maybe your p
On 01/28/2014 10:33 AM, Bruce Momjian wrote:
On Mon, Jan 27, 2014 at 07:48:33PM -0500, Tom Lane wrote:
Susan Cassidy writes:
This is 9.2
I'd bet a very good dinner that it isn't --- maybe your psql is,
but your server has to be pre-9.0. Try "select version();" to
see the actual version of th
On Tue, Jan 28, 2014 at 02:40:47PM -0300, Alvaro Herrera wrote:
> Bruce Momjian escribió:
> > On Mon, Jan 27, 2014 at 07:48:33PM -0500, Tom Lane wrote:
> > > Susan Cassidy writes:
> > > > This is 9.2
> > >
> > > I'd bet a very good dinner that it isn't --- maybe your psql is,
> > > but your serve
Bruce Momjian escribió:
> On Mon, Jan 27, 2014 at 07:48:33PM -0500, Tom Lane wrote:
> > Susan Cassidy writes:
> > > This is 9.2
> >
> > I'd bet a very good dinner that it isn't --- maybe your psql is,
> > but your server has to be pre-9.0. Try "select version();" to
> > see the actual version of
On Mon, Jan 27, 2014 at 07:48:33PM -0500, Tom Lane wrote:
> Susan Cassidy writes:
> > This is 9.2
>
> I'd bet a very good dinner that it isn't --- maybe your psql is,
> but your server has to be pre-9.0. Try "select version();" to
> see the actual version of the server you're connected to.
You
On Mon, Jan 27, 2014 at 12:12:13PM -0500, Tom Lane wrote:
> Bhushan Pathak writes:
> > In 9.1.3, this usage was upto 25MB with the same load on the same server.
> > With 9.2.4 it has jumped upto ~580 MB. We are monitoring the RES column
> > from top output to get the memory usage.
>
> On most ver
On Tue, Jan 28, 2014 at 7:53 AM, Andreas Lubensky wrote:
> That is an interesting approach. However, I see the problem that the
> functions would have to be removed when no longer needed. If that fails
> (broken connection etc.), they would be orphaned.
> Prepared statements are bound to the conne
That is an interesting approach. However, I see the problem that the
functions would have to be removed when no longer needed. If that fails
(broken connection etc.), they would be orphaned.
Prepared statements are bound to the connection, so when the connection
is closed they are gone.
On Thu, 20
28 matches
Mail list logo
