Re: DataType for storing pointlist (x,y,z)?
- From: "MP" <NoSpam@xxxxxxxxxx>
- Date: Tue, 1 Apr 2008 14:06:55 -0500
"Ralph" <nt_consulting64@xxxxxxxxx> wrote in message
news:eM6dnU4VA6e95m_anZ2dnUVZ_gqdnZ2d@xxxxxxxxxxxxxxx
"MP" <NoSpam@xxxxxxxxxx> wrote in message
news:eyB6L8BlIHA.5820@xxxxxxxxxxxxxxxxxxxxxxx
Hi Ralph,
is that the idea????
Yeah that was it, but you mentioned performance. Simple normacy would call
for a an associated table - but that might not work for your over-all
plan.
should I infer from those two sentences that a normalized db can be
performance wise slower than a single table?
There is always more than one way.
The secret is just like a shoe ad - "Just Do It" - if something isn't
working it will soon become very clear that plan B needs to be
investigated.
It's an iterative process. <g>
-ralph
well, then I'd take the kiss principle and try my first idea which brings me
back to the oq
(original question) <g>
what's the correct datatype for a field containing an array?
I'm assuming adVariant but not sure....
mark
.
- References:
- Re: DataType for storing pointlist (x,y,z)?
- From: Ralph
- Re: DataType for storing pointlist (x,y,z)?
- From: MP
- Re: DataType for storing pointlist (x,y,z)?
- From: Ralph
- Re: DataType for storing pointlist (x,y,z)?
- Prev by Date: Re: DataType for storing pointlist (x,y,z)?
- Next by Date: Problems with ADODB.Command and SQLServer 2005
- Previous by thread: Re: DataType for storing pointlist (x,y,z)?
- Next by thread: Problems with ADODB.Command and SQLServer 2005
- Index(es):
Loading