U++ forum: Welcome to the forum

Status & Roadmap

Authors & License

Funding Ultimate++

Search on this site

Search in forums

Home » U++ Library support » U++ SQL » PostgreSQL Attribute Foreign Key --> Bug?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Return to the default flat view

Create a new topic

Submit Reply

Re: PostgreSQL Attribute Foreign Key --> Bug? [message #17522 is a reply to message #17452]

Tue, 19 August 2008 13:55

captainc is currently offline

captainc
Messages: 278
Registered: December 2006
Location: New Jersey, USA

Experienced Member

In order to keep similarity of .sch files across all databases, we would not want to change the syntax that to define a reference. If this is a true statement, then we would need some sort of additional macro that would take a character string "TABLE.COLUMN" and turn it into "TABLE(COLUMN)" for only postgresql (and any other databases that require this syntax).

What is the best way to go about this?

Can we have a PostgresqlSchema class extend the Schema class and override Attribute and InlineAttribute to perform the replacement?

[Updated on: Tue, 19 August 2008 14:17]

Report message to a moderator

Send a private message to this user

[Message index]

		PostgreSQL Attribute Foreign Key --> Bug? By: captainc on Fri, 15 August 2008 17:22
		Re: PostgreSQL Attribute Foreign Key --> Bug? By: zsolt on Fri, 15 August 2008 19:05
		Re: PostgreSQL Attribute Foreign Key --> Bug? By: captainc on Tue, 19 August 2008 13:55
		Re: PostgreSQL Attribute Foreign Key --> Bug? By: captainc on Tue, 19 August 2008 20:43
		Re: PostgreSQL Attribute Foreign Key --> Bug? By: mirek on Thu, 21 August 2008 16:53

Previous Topic:	Connecting to multiple databases.
Next Topic:	Count error

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

PDF

]

Current Time: Fri Aug 15 17:10:48 CEST 2025

Total time taken to generate the page: 0.08407 seconds