Messages posted by: Sean_L

Jim_ wrote:Advanced Server uses an update service to apply patch releases instead of a manual overlay like Standard Server and the Community Editions. When you install Advanced Server it will ask you if you want to check for updates. This will apply the latest patch release. Future patches can be applied through the same update mechanism in the DBA Management Server.

So ... if I have the current release of Advanced Server and have applied all of the updates, the full text indexing and searching support should be available? Or, looking at it a different way, if full text indexing isn't working (e.g. it can't find the tsvector and tsquery types), that means I haven't applied all of the updates?

Thanks!

-Sean

Hi,
I'm trying to use PostgresPlus AS in conjunction with the newer support in Postgres for full text searches. I saw that PostgresPlus community edition was released with Postgres 8.3.5, but Advanced Server is still using 8.3.0. Is there a timeline for the next release PGPlus AS?

Thanks.

-Sean

I'm really hoping somebody can help us out. We're using EDB version 8.1e. We know oracle pl/sql fairly well, but are struggling with a postgres function. We can't get a ""LANGUAGE 'plpgsql'" to work to simulate the setof return data.

Well, I'm no PGPL/SQL expert myself, but if I understand your problem correctly, you need the function to:

A) Call the ftd_apps.search_inv_trk_prepare
B) Use the results of that function call as part the where clause in a select
C) Return the results of the select

Here's the basic idea. I'm not sure what datatype the search_inv_trk_prepare function returns, so you'll need to adjust this based on that datatype. But it should point you in the right direction, I hope.

Hope that helps.

You can also read about this more in the Postgres documentation:

http://www.postgresql.org/docs/8.3/static/plpgsql-control-structures.html#PLPGSQL-STATEMENTS-RETURNING

-Sean

I was testing the MySQL Migration process and I ran into an issue with columns that are defined as enum in MySQL. While Postgres doesn't support the enum type, it does offer two equivalents via custom data types and CHECK constraints. I tried using the Migration tool two ways.

1) Migrate both the schema and data from a MySQL table with an enum column to a clean Postgres database. Migration failed with an error about the enum column.

2) Create the table in Postgres and define the enum column as varchar with a CHECK constraint. Migrate just the data from MySQL to the empty table in Postgres. Migration failed with the same error.

Am I doing something wrong? Is this a known issue? Other than ALTERing the MySQL tables that use enum columns, are there other workarounds?

Any advice would be greatly appreciated! Thanks.

-Sean