SSQL multiple definition errors

#1

thanks Mark
i'm in the process of trying your solution! - i am still wondering if there
is a solution which does not involve tampering with the library as having
"portable" SSQLs seems like a pretty fundamental requirement to me
terry

Quote:

From: "Mark Merendino" <Mark.Merendino (AT) mcdata (DOT) com
To: "terry johnston" <tmjohnston (AT) hotmail (DOT) com>,<plusplus (AT) lists (DOT) mysql.com
Subject: RE: SSQL multiple definition errors
Date: Wed, 14 Sep 2005 06:47:23 -0600

Not sure if this is the redef problem you are refering to but I tackled
a redef problem a ways back. Check it out here...

http://lists.mysql.com/plusplus/4295

-----Original Message-----
From: terry johnston [mailto:tmjohnston (AT) hotmail (DOT) com]
Sent: Wednesday, September 14, 2005 5:46 AM
To: plusplus (AT) lists (DOT) mysql.com
Subject: SSQL multiple definition errors

thanks Chris
i want to create some objects in my library that contain SSQL structures
- so i might have a widget class that contains an SSQL stock & an SSQL
price - the widget object would be used in the higher level appication,
requiring knowledge of the SSQL definitions, hence the redefinition
problem - can i do this?
terry

From: Chris Frey <cdfrey (AT) netdirect (DOT) ca
To: plusplus (AT) lists (DOT) mysql.com
Subject: Re: SSQL multiple definition errors
Date: Wed, 14 Sep 2005 05:01:19 -0400

On Wed, Sep 14, 2005 at 08:21:23AM +0000, terry johnston wrote:
Hello all
i am trying to use some SSQL structures in a library built around
mysql++ &
cannot seem to avoid multiple definition errors - i have seen some
comments
saying that changes may be made to the SSQL macros at some point but

can anyone please tell me if there are workarounds to achieve this
in the short-term - if not, how do people use SSQL in the context of

a larger project?

I believe the main idea is to create an application-specific API that
you use for all your database interaction. The API implementation is
done in one .cpp file, and you only need to include SSQLS once.

The other advantage to doing it this way is that you can reimplement
your database routines to use different database backends, if you need
to.

- Chris

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe:
http://lists.mysql.com/plusplus?unsu...mail (DOT) com

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe:
http://lists.mysql.com/plusplus?unsu... cnt (DOT) com

SPECIAL NOTICE

All information transmitted hereby is intended only for the use of the
addressee(s) named above and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution
of confidential and privileged information is prohibited. If the reader
of this message is not the intended recipient(s) or the employee or agent
responsible for delivering the message to the intended recipient, you are
hereby notified that you must not read this transmission and that
disclosure,
copying, printing, distribution or use of any of the information contained
in or attached to this transmission is STRICTLY PROHIBITED.

Anyone who receives confidential and privileged information in error should
notify us immediately by telephone and mail the original message to us at
the above address and destroy all copies. To the extent any portion of
this
communication contains public information, no such restrictions apply to
that
information. (gate02)

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw

#2

terry johnston wrote:

Quote:

i want to create some objects in my library that contain SSQL structures
- so i might have a widget class that contains an SSQL stock & an SSQL
price - the widget object would be used in the higher level appication,
requiring knowledge of the SSQL definitions, hence the redefinition
problem - can i do this?

Not as the SSQLS macros are presently implemented.

There's no shortage of knowledge of the problem's nature, nor of hacky
fixes for the problem. What is wanted is an elegant fix.

You can find some suggestions for fixes in the Wishlist. The only
reason the problem has gone unfixed for so long is that most people just
work around it somehow. But if you're determined to use the SSQLS
definitions throughout your program, it seems you have the motivation to
fix it.

If I were to tackle this problem, I'd try the "sub-macro" suggestion
first, then the "MFC macro" one next, then the "add a parameter" and if
all that failed I'd resort to the redesign option. Also, there's
another Wishlist item two down from that (the "boilerplate" one) which
may also inform your efforts.

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SSQL multiple definition errors

mailing.database.mysql-plusplus mailing.database.mysql-plusplus

SSQL multiple definition errors - 09-14-2005 , 08:59 AM

Re: SSQL multiple definition errors - 09-14-2005 , 06:53 PM