| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Arturo Pie Joa <arturotd08(at)yahoo(dot)ca> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Using incorrect default-value type |
| Date: | 2012-10-16 03:03:06 |
| Message-ID: | 14372.1350356586@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Arturo Pie Joa <arturotd08(at)yahoo(dot)ca> writes:
> Is it ok to do name overloading in postgreSQL? or is thatnotrecommended at all? Could I find some issues later by doing name overloading?
People use it all the time ... and get burnt some of the time.
> We are doing this because we are using different collations on each schema, and our ORM doesn't support custom domains, so we are just overloading "text".
Maybe you need a better ORM. But it's not clear to me why you'd need
domains for this anyway --- can't you just attach a collation property
to each table column?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Deven Thaker | 2012-10-16 04:24:06 | Application takes longer time to fetch large no of records from Postgresql 9.0.3 |
| Previous Message | Daniel Baktiar | 2012-10-16 02:51:36 | Re: PostgreSQL JDBC Driver for corresponding JDK/JVM. |