Problem with warnings

[Ruslan Zasukhin]

On 6/9/07 11:11 PM, "Jörg Pressel" <joergp at three-2-one.com> wrote:

Hi Jörg, 
 
> my app used to work just fine and I don't know why Valentina 3.3
> comes up with warnings. First warnings I get are in a select:
> 
> SELECT Distinct Artist,Tracks.Artist_Ptr,UpperArtistShort FROM
> Tracks,Artists Where Album_Ptr->CoverPictureL Is Not Null order by
> UpperArtistShort
> 
> Warnings:
> Get Field : No field with name Album_Ptr
> Get Field : No field with name Artist
> Get Field : No field with name UpperArtistShort
> 
> But that's simply wrong. Valentina used to find the fields itself ­
> Album_Ptr is Tracks.Album_Ptr,
> Artist is Artists.Artist,
> UpperArtistShort is Artists.UpperArtistsShort.
> 
> Do I have to add the table names, even if field names are unique
> within a Select?
> 
> Huh, and why there is no warning for CoverPictureL?
> 
> Never I've added table names to fields in SQLSelect statements where
> it was obvious. Do I have to rework every single Select statement??

Well, this is new feature. Yes this warns looks to be wrong.

Please report into Mantis, and add some simple db with query that reproduce
it.


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]