Обсуждение: Sql Anywhere to PostgreSQL?
Has anyone ever done a conversion from Sql Anywhere to PostgreSQL? I have a task to investigate what this would take.
Also, the Sql Anywhere database stores image files in the database as long binary types. What would be the best format to store these in PostgreSQL?
Also, while all of my current PG clusters are on RH linux, if this project went forward, it would have to run on Windows 2k. Will the windows version of PG run on 2k, and are there any special caviates running on this platform?
Thanks,
Chris
PG 8.1.3
RH 4.0 AS
Also, the Sql Anywhere database stores image files in the database as long binary types. What would be the best format to store these in PostgreSQL?
Also, while all of my current PG clusters are on RH linux, if this project went forward, it would have to run on Windows 2k. Will the windows version of PG run on 2k, and are there any special caviates running on this platform?
Thanks,
Chris
PG 8.1.3
RH 4.0 AS
Chris Hoover wrote: > Has anyone ever done a conversion from Sql Anywhere to PostgreSQL? I > have a > task to investigate what this would take. > > Also, the Sql Anywhere database stores image files in the database as long > binary types. What would be the best format to store these in PostgreSQL? That would be bytea or blob depending on your exact needs. > Also, while all of my current PG clusters are on RH linux, if this project > went forward, it would have to run on Windows 2k. Will the windows version > of PG run on 2k, and are there any special caviates running on this > platform? PostgreSQL 8.0 and above runs on windows and is available in a pre-configured windows installer package to install like other software. The main catch is the windows version is somewhat newer and less tested than the *nix versions. (previous versions on windows where the *nix source built on top of cygwin) -- Shane Ambler pgSQL@007Marketing.com Get Sheeky @ http://Sheeky.Biz
> Has anyone ever done a conversion from Sql Anywhere to PostgreSQL? I have a > task to investigate what this would take. Biggest problem areas I see would be stored procedures and the many SQL differences. If you use stored procedures, they will need to be completely rewritten. The SQL differences will get you too; someone who knows both SQLA and PostgreSQL will have to review line-by-line. Stuff like SQLA's "current timestamp" vs PostgreSQL "current_timestamp". Or, limiting returned rows (SQLA: SELECT TOP 10 * FROM ... vs PostgreSQL: SELECT * FROM ... LIMIT 10). Just two examples. Where standards exist, PostgreSQL is much more standard than Sybase.