Re: Visual Studio Query Builder filter

Actually, the Query Builder seems to be almost completely broken with
version 8.01.02.00. In previous versions I could use it to define simple
filters etc..

With 8.01.02.00 I can only use the Query Builder to generate a
bare-bones SELECT/INSERT/... I found I can then close the generate
wizard and make a more advanced query by hand in the properties window
without everything breaking. Walking on tip-toes though!

Patrick

PS. Sorry, it's probably not so much the fault of psqlODBC developers as
the result of having to fit the Microsoft mould...
> Apologies if this is largely a Visual Studio 2005 question. I'm
> posting it here because I assume my problem is caused by the
> interaction between psqlODBC and Visual Studio. I'm using psqlODBC
> 8.01.02.00.
>
> When using the graphical Query Builder tool, you can specify a filter
> for your query. For example, if you specify the filter for table
> column x as " = sometext' then you get:
> WHERE x = 'sometext'
> in your query.
>
> All well and good if the column is of type text, but if the column is
> of type Boolean I can't figure out how to get the damn thing to accept
> my filter. For example:
> " = 't'"
> " = t"
> " = true"
> etc...
> all don't work, saying that the data is of the wrong type.
>
> Ok, so you're wondering why I don't just write my query the good old
> fashioned way? The problem is if the Query Builder doesn't like your
> query, it spits the dummy when it tries to generate the FillBy and
> GetBy queries needed to use VS 2005 TableAdaptors.
>
> The only workaround I've found so far is to create a dummy function
> that always returns true and use that in the filter, eg.
> " = alwaysTrue(12345)"
>
> Any ideas on how to get it to accept my filter as boolean so I don't
> have to use this workaround?
>
> Regards,
>
> Patrick
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>       choose an index scan if your joining column's datatypes do not
>       match