Re: Terminology question

pamelafluente_at_libero.it wrote:

> Hi Bob. My perspective is that of an application programmer. I just
> wanted simple names to put on my interface to denote those objects, for
> easy identification from the user part.

In that case, I suggest you are asking in the wrong newsgroup. The question is more appropriate in a newsgroup devoted to usability or human-computer interaction (HCI).

> For instance, the user might have a collection of objects he reuses to
> get connected to a DBMS (those I call "connections").

There are a number of names that have been used for similar things: channels, connections, sessions. For some reason, connect seems to have taken hold among database implementations. I find "connecting to a database" wrong-minded and borderline anthropomorphizing.

> I was wondering how to call the object which stores both connection
> info and the user "rule" to extract data (usually a SELECT or a pl/sql
> program) . It represents at a logical level a bunch of data. Only when
> actually executed it "becomes" real data.

In a database theory newsgroup, the logical level means something very specific. It strikes me that the artifacts you describe are physical artifacts of your application's implementation and not logical at all.

> -P
>
> PS
> btw, I am asking because I am italian :)

That should give you an advantage over native speakers of english.

> Bob Badour ha scritto:
>

>>pamelafluente_at_libero.it wrote:
>>
>>>Hi.
>>>
>>>I need to give a name to some categories of objects in a program. Name
>>>must be clear to the user and possibly 1 word.
>>>
>>>  o1 = Database  --> "database"
>>>  o2 = Connection to a Database (connection string + login info)   -->
>>>"connection"
>>>  o3 = Connection to Database + SQL/custom program to extract data
>>>--> "??"
>>>
>>>Question.
>>>
>>>What is the best name for o3. I wanted to call it a "datasource", but
>>>some people are arguing that "datasource" is usually the same as
>>>database.
>>>
>>> What is your suggestion for a clear and meaningful naming of these
>>>objects ?
>>
>>I haven't a clue what you are talking about. A database is a set of
>>facts. How one 'connects' to that is beyond me.
>>
>>A client computer can connect to a server.
>>A database management system can authenticate a user.
>>
>>I suggest you focus on mastering the basics before inventing new
>>terminology.