Re: Converting MySQLdatabases to postgresql
From: Christopher Browne (cbbrowne_at_acm.org)
Date: 07/19/04
- Next message: project2501: "Re: assured dns resolutions (secure)"
- Previous message: Christopher Browne: "Re: Converting MySQLdatabases to postgresql"
- In reply to: rassle: "Re: Converting MySQLdatabases to postgresql"
- Next in thread: Juhan Leemet: "Re: Converting MySQLdatabases to postgresql"
- Reply: Juhan Leemet: "Re: Converting MySQLdatabases to postgresql"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 19 Jul 2004 13:52:49 GMT
Quoth rassle <itmanager@expamet.co.uk>:
> There are differences, but not in data types or in SQL statements.
What????
The essential differences _are_ in data types, and handling of data
typing, as well as in the forms of SQL accepted by the respective
systems.
They are WILDLY different, particularly in the degree of respect the
projects have for ANSI standards.
-- select 'cbbrowne' || '@' || 'cbbrowne.com'; http://www.ntlug.org/~cbbrowne/postgresql.html (eq? 'truth 'beauty) ; to avoid unassigned-var error, since compiled code ; will pick up previous value to var set!-ed, ; the unassigned object. -- from BBN-CL's cl-parser.scm
- Next message: project2501: "Re: assured dns resolutions (secure)"
- Previous message: Christopher Browne: "Re: Converting MySQLdatabases to postgresql"
- In reply to: rassle: "Re: Converting MySQLdatabases to postgresql"
- Next in thread: Juhan Leemet: "Re: Converting MySQLdatabases to postgresql"
- Reply: Juhan Leemet: "Re: Converting MySQLdatabases to postgresql"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]