|
|
RE: [enhydra] Why not bigint instead of numeric(19,0) in postgresql and usi: msg#00017java.enhydra.general
Madl Alfred - Together AT píše v Po 26. 09. 2005 v 15:34 +0200: > Enhydra 7.0 will have AMD64/EM64T support (main feature of this release) for > all components BTW, I run Enhydra 5.1.15 on AMD64 successfully - the only thing that doesn't work well is the Enhydra Multiserver's wrapper that is distributed as i386 compiled binary without source code. Petr -- You receive this message as a subscriber of the enhydra@xxxxxxxxxxxxx mailing list. To unsubscribe: mailto:enhydra-unsubscribe@xxxxxxxxxxxxx For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | RE: [enhydra] Why not bigint instead of numeric(19,0) in postgresql and using Long instead of BigDecimal, Madl Alfred - Together AT |
|---|---|
| Next by Date: | Re: [enhydra] Why not bigint instead of numeric(19,0) in postgresql and using Long instead of BigDecimal, João Paulo Ribeiro |
| Previous by Thread: | RE: [enhydra] Why not bigint instead of numeric(19,0) in postgresql and using Long instead of BigDecimal, Madl Alfred - Together AT |
| Next by Thread: | Re: [enhydra] Why not bigint instead of numeric(19,0) in postgresql and using Long instead of BigDecimal, João Paulo Ribeiro |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |