Re: [GENERAL] Allowing SYSDATE to Work
| От | Josh Berkus |
|---|---|
| Тема | Re: [GENERAL] Allowing SYSDATE to Work |
| Дата | |
| Msg-id | 200611181534.31729.josh@agliodbs.com обсуждение |
| Ответ на | Re: [GENERAL] Allowing SYSDATE to Work ("Matt Miller" <pgsql@mattmillersf.fastmail.fm>) |
| Ответы |
Re: [GENERAL] Allowing SYSDATE to Work
|
| Список | pgsql-hackers |
Matt, > I now agree completely. My purpose is to migrate Oracle databases to > Posgres, and I had thought that Oracle didn't support CURRENT_DATE, > CURRENT_TIMESTAMP, and so on. However, I've just learned otherwise. So, > I think the proper migration process for a production database would be > to first change the Oracle DB to use CURRENT_DATE (or some other > standard psuedo column), since that will work properly under both Oracle > and Postgres. Yep, or use the Orafce project. We're happy to support compatibility syntax in completely separate add-in projects. Just not in the core code. -- Josh Berkus PostgreSQL @ Sun San Francisco
В списке pgsql-hackers по дате отправления: