Fri, 02 Mar 2012 19:00:30, Roger Binns wrote:
> On 02/03/12 15:20, Steven Russell wrote:
>> I obviously don't expect the duplicate results here. If you create the
>> table without the UNIQUE clause, then the results are as expected (1
>> and 2 both only show up once).
>
> BTW the team agreed it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/03/12 15:20, Steven Russell wrote:
> I obviously don't expect the duplicate results here. If you create the
> table without the UNIQUE clause, then the results are as expected (1
> and 2 both only show up once).
BTW the team agreed it was a bug
Simon Slavin wrote and quoted:
>> Would the output of 'PRAGMA compile_options;' be sufficient ?
>
> That's a cute and useful feature I had forgotten. It would be sufficient to
show the preprocessor variable values that were in effect as the amalgamation was
compiled. However, for something th
On 3 Mar 2012, at 12:46am, Larry Brasfield wrote:
>> On 3 Mar 2012, at 12:29am, Larry Brasfield
>> wrote:
>>
>> > That's approaching a pretty good "bug" report. However, I would suggest a
>> > little more to promote a resolution of this problem. You do not state the
>> > compilation optio
On 3 Mar 2012, at 12:29am, Larry Brasfield wrote:
> That's approaching a pretty good "bug" report. However, I would suggest a
little more to promote a resolution of this problem. You do not state the compilation
options. Optimization settings and preprocessor variable settings are critical
On 3 Mar 2012, at 12:29am, Larry Brasfield wrote:
> That's approaching a pretty good "bug" report. However, I would suggest a
> little more to promote a resolution of this problem. You do not state the
> compilation options. Optimization settings and preprocessor variable
> settings are cr
Steven Russell wrote:
I just grabbed the 3.7.10 amalgamation source and built it, but have run into
an issue where DISTINCT doesn't appear to actually return distinct values on a
table that includes a UNIQUE clause. It unexpectedly returns duplicates
instead.
My build environment is:
- Mac
I just grabbed the 3.7.10 amalgamation source and built it, but have run into
an issue where DISTINCT doesn't appear to actually return distinct values on a
table that includes a UNIQUE clause. It unexpectedly returns duplicates
instead.
My build environment is:
- Mac OS X 10.6.8
- Xcode 3.2
8 matches
Mail list logo