[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNUe-dev] gnue_id, extending the existing DB tables
From: |
malek |
Subject: |
Re: [GNUe-dev] gnue_id, extending the existing DB tables |
Date: |
Mon, 31 Jan 2005 15:31:56 +0100 |
User-agent: |
Internet Messaging Program (IMP) 3.2.2 |
there's an other pb
xml-rpc don't support bigint (http://www.xmlrpc.com/spec).
so you would have to convert to string anyway for the clients.
(i don't know about the other protocol supported soap, pyro...)
thanks,
lekma
Quoting Fehér János <address@hidden>:
> 2005-01-30, v keltezéssel 22.48-kor Reinhard Mueller ezt Ãrta:
> > Am Sonntag, den 30.01.2005, 17:36 +0100 schrieb Fehér János:
> > > But first of all, I have question: why do you using string
> > > type for gnue_id in the database layer? It's not very efficient
> > > on most of the DBMS. They like integers for this, I really think
> > > 64bit unsigned integers are should be enough. What was the reason?
> >
> > We have to select something that all databases support, and I'm
> > absolutely not sure all databases support 64 bit integers on all
> > platforms.
>
> Oracle, SAPDB (MySQL MaxDB) can do it,
> MySQL has BIGINT 8 bytes column type.
> PostgreSQL has arbitrary precision numbers.
>
> I'm not familiar with the others but I think they could do
> numerical solution.
> --
> ,_____ _ ____ ___ _____ ___ ___ _____ .
> | | | :|_|| | || :| | | || || || || __: | Fehér János
> | | | || || || || | | |: :| --:|---':__ | | -----------------
> | ___ ||_||_|__|:___|:_____:|___|| || ||_____| | ` vezetŠprogramozó
> http://mindworks.hu - networking.it.solutions : ` ügyvezetÅ
>
>
>
> _______________________________________________
> Gnue-dev mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/gnue-dev
>