• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: On SQL fully qualified names and how to implement them in EO models
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: On SQL fully qualified names and how to implement them in EO models


  • Subject: Re: On SQL fully qualified names and how to implement them in EO models
  • From: Ângelo Andrade Cirino <email@hidden>
  • Date: Mon, 04 May 2015 22:54:11 -0300

Hi Dave,

I understand your reasoning on using UserInfo dictionaries, but when I look at the plugins code I imagine the use o methods like

myEntity.qualifiedName() => SCHEMA.TABLE
myEntity.qualifiedQuotedName() => “SCHEMA”.”TABLE"
myAttribute.qualifiedName() => TABLE.COLUMN
myAttribute.fullyQualifiedName() => SCHEMA.TABLE.COLUMN

This would spare some work in the composition of the names in the generation of expressions and SQL code. Also, this methods, as KVC, would be accessible for every other use that is needed, for example in template parsing.

For me, the more explicit the better.

Angelo

> Em 04/05/2015, à(s) 22:43, David Avendasora <email@hidden> escreveu:
>
> I'm not sure that modifying the plugins to use a UserInfo dictionary entry would be more likely to cause problems than modifying them to use a new top-level entry.
>
> There is already a _entityModeler key that is added to the various UserInfo dictionaries to hold things like multiple connection dictionaries and modelDoc that are additions to the apple-published spec.
>
> With that said, in this particular situation it seems more likely that the individual plugins should be modified to deal with multiple components in the table name. As you noted, different DBs have different levels of organization available. Schemas, Table Spaces, Databases, OracleWhatzit, etc. simply adding a key for schema is an oversimplification that begs for misuse (most likely by me).
>
> Dave
>

Ângelo Andrade Cirino
email@hidden

"O homem sensato se adapta ao mundo. O insensato insiste em tentar adaptar o mundo a ele. Todo o progresso depende, portanto, do homem insensato"
Sir George Benard Shaw

"The reasonable man adapts himself to the world: the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man."
Sir George Benard Shaw



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >On SQL fully qualified names and how to implement them in EO models (From: Ângelo Andrade Cirino <email@hidden>)
 >Re: On SQL fully qualified names and how to implement them in EO models (From: "Morris, Mark" <email@hidden>)
 >Re: On SQL fully qualified names and how to implement them in EO models (From: Ângelo Andrade Cirino <email@hidden>)
 >Re: On SQL fully qualified names and how to implement them in EO models (From: David Avendasora <email@hidden>)

  • Prev by Date: Re: On SQL fully qualified names and how to implement them in EO models
  • Next by Date: Reverse engineering with PostgreSQL
  • Previous by thread: Re: On SQL fully qualified names and how to implement them in EO models
  • Next by thread: Re: On SQL fully qualified names and how to implement them in EO models
  • Index(es):
    • Date
    • Thread