Currently it seems like that dot is not considered as a word delimiter
by the english parser.
lawdb=# select to_tsvector('english', 'Mr.J.Sai Deepak');
to_tsvector
-
'deepak':2 'mr.j.sai':1
(1 row)
So the word obtained is mr.j.sai rather than three words
On May 29, 2009, at 5:16 PM, Greg Stark wrote:
On Fri, May 29, 2009 at 11:03 PM, David E. Wheeler da...@kineticode.com
wrote:
On May 29, 2009, at 2:52 PM, Josh Berkus wrote:
a) the ability to push a schema onto the current search path
b) the ability to pull a schema off the current search
Bruce Momjian wrote:
Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
It would be nice to have pg_migrator handle this, especially if we could
do it in parallel. Then we just have to warn users that migrating a
database with tsvector columns takes significantly longer. That
On Sat, May 30, 2009 at 1:11 PM, Bruce Momjian br...@momjian.us wrote:
I have discovered a simpler solution using ALTER TABLE and calling a
conversion function:
test= CREATE TABLE tsvector_test(x tsvector);
CREATE TABLE
test= ALTER TABLE tsvector_test ALTER COLUMN x TYPE
Hi,
Le 30 mai 09 à 16:02, Greg Stark a écrit :
On Sat, May 30, 2009 at 1:11 PM, Bruce Momjian br...@momjian.us
wrote:
I have discovered a simpler solution using ALTER TABLE and calling a
conversion function:
test= CREATE TABLE tsvector_test(x tsvector);
CREATE TABLE
Bruce Momjian br...@momjian.us writes:
I have discovered a simpler solution using ALTER TABLE and calling a
conversion function:
test= CREATE TABLE tsvector_test(x tsvector);
CREATE TABLE
test= ALTER TABLE tsvector_test ALTER COLUMN x TYPE tsvector
test- USING
On Fri, 2009-05-29 at 21:16 -0300, Euler Taveira de Oliveira wrote:
Simon Riggs escreveu:
And for them, it hasn't been completely fixed. That point was not made
by patch author or committer, leaving the impression it was now
completely safe, which, I truly regret to say, is not correct.
Dimitri Fontaine wrote:
Hi,
Le 30 mai 09 ? 16:02, Greg Stark a ?crit :
On Sat, May 30, 2009 at 1:11 PM, Bruce Momjian br...@momjian.us
wrote:
I have discovered a simpler solution using ALTER TABLE and calling a
conversion function:
test= CREATE TABLE tsvector_test(x
Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
I have discovered a simpler solution using ALTER TABLE and calling a
conversion function:
test= CREATE TABLE tsvector_test(x tsvector);
CREATE TABLE
test= ALTER TABLE tsvector_test ALTER COLUMN x TYPE tsvector
Bruce Momjian wrote:
Just thinking some more about the idea to get all those post-
processing steps running in parallel, it's occurring to me that we
have all we need already: would it be possible for pg_migrator to
issue a schema only script with a catalog, in the custom archive
Bruce Momjian wrote:
Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
I have discovered a simpler solution using ALTER TABLE and calling a
conversion function:
test= CREATE TABLE tsvector_test(x tsvector);
CREATE TABLE
test= ALTER TABLE tsvector_test ALTER COLUMN x
--On Samstag, Mai 30, 2009 00:47:16 +0300 Hannu Krosing
ha...@2ndquadrant.com wrote:
And we can also escape the need to uncompress TOAST'ed fields - just
markup the compression as another \c at the beginning of data.
Hmm i thought about that, but that seems only to make sense if there is an
--On Freitag, Mai 29, 2009 11:06:28 +0300 Peter Eisentraut
pete...@gmx.net wrote:
Btw., I have started to write some code for that.
Cool. Let me know if i can help out somewhere.
--
Thanks
Bernd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
Simon Riggs escreveu:
And for them, it hasn't been completely fixed. That point was not made
by patch author or committer, leaving the impression it was now
completely safe, which, I truly regret to say, is not correct.
Simon, could you point out what the patch does not do? If we can't fix it
Bruce Momjian br...@momjian.us writes:
Tom Lane wrote:
I think this is basically a large-caliber foot gun. You're going to
pretend that invalid data is valid, until the user gets around to fixing
it?
What choice do we have?
Create a fake data type, just as you said before.
Here's an updated version of my patch from last night.
http://archives.postgresql.org/message-id/603c8f070905292048y804d505wf701214e7b81f...@mail.gmail.com
In addition to the changes mentioned there, this removes a completely
unused argument from show_scan_qual() and two redundant ones from
On Sat, May 30, 2009 at 6:23 PM, Bruce Momjian br...@momjian.us wrote:
I think this is basically a large-caliber foot gun. You're going to
pretend that invalid data is valid, until the user gets around to fixing
it?
What choice do we have?
Well you can store the data in a new fake data type
I'm trying to connect ruby to postgres on ubuntu and the only link I found that
has the library is down. Does anyone have the postgres library for ruby? Or
direct me to it?
Justin Darby Carrera
Database Programmer/Analyst
MED-Department of Medical Social Sciences
Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
Tom Lane wrote:
I think this is basically a large-caliber foot gun. You're going to
pretend that invalid data is valid, until the user gets around to fixing
it?
What choice do we have?
Create a fake data type, just as you said
Greg Stark wrote:
On Sat, May 30, 2009 at 1:11 PM, Bruce Momjian br...@momjian.us wrote:
I have discovered a simpler solution using ALTER TABLE and calling a
conversion function:
? ? ? ?test= CREATE TABLE tsvector_test(x tsvector);
? ? ? ?CREATE TABLE
? ? ? ?test= ALTER TABLE
Greg Stark wrote:
On Sat, May 30, 2009 at 6:23 PM, Bruce Momjian br...@momjian.us wrote:
I think this is basically a large-caliber foot gun. ?You're going to
pretend that invalid data is valid, until the user gets around to fixing
it?
What choice do we have?
Well you can store the
21 matches
Mail list logo
