DSN with MySQL

[jund]

ZEN-CART Version 1.3.7
Server Microsoft IIS Server 6.0
PHP Version 5.2.1

The web site www.imagesbydavido.com consists of two 'sections'; a Gallery 'section' and ZEN-CART store.

The Gallery uses an Access database for managing the images via a DSN.

The store uses the MySql database for managing the store. It does not use a DSN. It uses the connection string provided by you all.

Both work the way they should.


It would be convenient for me to include some of the information in the store's database on the Gallery's 'section.'

My question is would it be a bad thing to use a DSN on the MySQL Zen-Cart database along with the current connection? The host has provisions for both. That is to access the MySql database two ways - the 'string' (dsn'less) and DSN.

Thank you,
jund

[BlindSide]

Why not just run Gallery in the MySQL server alongside Zen-Cart? It's built for MySQL by default anyway.

If you have to run in Access for some reason (and it better be a darn good one), that's fine. But my point in asking is why try to solve a problem that you don't have to face in the first place?

[jund]

I do not understand... Perhaps you think the gallery I mentioned is a pre-made gallery? It is not... it was one created for my client according to his specs.
Thank you,
jund

[jund]

Guess I will have to ask again...

My question had nothing to do with Access. My question was, "could I use a DSN connection to the ZEN-CART database at the same time I am using the DSN'less connection that is already in place?" It is a simple question - and my logic tells me it will work fine - but, I just wanted to check prior to implementing it.

I clearly do not understand this comment or the motivation to say it.

"If you have to run in Access for some reason (and it better be a darn good one), that's fine. But my point in asking is why try to solve a problem that you don't have to face in the first place?"

The site is built and running - created the Gallery first (May 2006) and used Access instead of MySQL because I had many apps the client could use to keep his gallery current. The cart was ColdFusion at that time...

The Gallery performed flawlessly, and, it works great - don't know why someone would use the phrase "and it better be a darn good one" as if using a Windows Server and a Microsoft app is a sin.

However, the ColdFusion Cart proved to be a nightmare - promises made, promises not kept... so I went looking for a PHP Cart. I started with OS Commerce, but the lack of support was intolerable. (it is a fine cart however).

When I found ZEN-CART - like the rest of us - I found the support outstanding, the folks knowledgeable, and went to work using PHP instead of CFM.

I didn't give this long dissertation to entertain or enlighten or even tout my client's site... it is just simply a mystery to me why someone would jump into a question with an answer like the one I received. Not only is it against a particular app... it is against what ZEN-CART is all about... positive support - not condescending commentary.

Puzzled with the response....

jund

[BlindSide]

LOL, my bad. I was referring to this...

http://gallery.menalto.com

"Gallery" is an open source photo management program that runs on PHP and MySQL. I wasn't trying to diss your decision to use Access, but rather using Access in conjunction with this program. In that case, it definitely should be a solid reason for using Access in place of the native MySQL support. My apologies for the misunderstanding.

[jund]

Blindside,

You have put new meaning in the term 'respect.' You have my sincere thanks for respecting yourself enough to publicly apologize. Thank you.

May I please indulge you for a few minutes? I would like to share this saga with you. It is not an egocentric bit of rhetoric - just a tale I want to share.

Early in the development of the site, I tried 'Gallery' and 'Coppermine.'
At the same time, I was developing a separate store (Gallery and Coppermine did not have shopping carts). My client wanted to build the site so that he could show off his works in a pure non-sales-pressure gallery, with provisions to be linked to a totally independent 'store.'

My biggest issue was that no gallery application met the demands of a store (downloads, printing, payment and receipt management, etc.); and no store met the demands of a true gallery (the images in the gallery should look good enough to eat - sorry for the dumb cliche' - and at the same time, none of the store's produced images were of adequate quality for the gallery).

So I built the gallery using an App called ACDSee Pro. It did all the things that he needed done, and it produced reasonable html (xhtml) documents - thumbnails, mid-sized, and full-sized images. I modified the xhtml, changed it to CFM and hooked it up to his already configured Access database. That was really fun! And, at the same time I was busy messing things up big time by trying to attach this mess to a CFM storefront... barf!

CFM storefronts (at least those who build their own - similar to open source) were not readily available - so I changed the entire gallery from CFM to PHP - another exciting adventure into the unknown (makes your handle 'Blindside' a reality - smile). It seems that PHP had lots of storefronts and galleries...

My first PHP encounter was with OSCommerce, primarily because PayPal endorsed it. However, after a few weeks of many issues I realized OSCommerce was not adequately supported. But, my client liked the storefront it produced. And, one more obstacle was in the way - the gallery had its own set of high qulity images, and the store produced its own separate set of mediocre images- and I was not smart enough to figure out how to merge the two sets.

Along came ZEN CART - like an answer to a maiden's prayer...
It was absolutely exciting again... I still had the issue of two separate databases and two separate image files - until in the middle of one of the darkest nights I stumbled onto the image folders in ZC and decided to use them for the gallery - a total paradigm shift . Now, my client puts his beautiful images into the store folders - and when a person is viewing the gallery side, the images he/she views are from the store folder. Bear in mind, the gallery does not process these images, so no harm no foul.
However, the store does process the same (gallery) images - but that is ok... the customer can go from the gallery to the store having seen the image the way my client wants them to see them - just like in a real gallery... and when he clicks to go to the store, he sees 'samples.'

It is still really rough around the edges... but it is coming together, thanks to folks like you and others in this grand place known as ZEN CART. You had the courage to stick your neck out - and be honest with me - you done real good... and I learned from you.

Thank you,
jund

[DrByte]

DSN is just another communication method. Using it instead of the default methods should have no specific drawback.

You might consider whether having the application making database calls via two methods might also mean you're making a lot more database calls than necessary. This is fine if your database server can handle the query load.
Just consider this a suggestion to review your database queries to be sure you're not making needless duplicate queries if you make such a change.

[jund]

Dr. Byte,

Nice! It is great to hear from you again. Thank you for looking at the note. Your advice is well taken - in the 'fun of the game' I completely overlooked the possibility of too many calls to the database... thank you. It is horribly myopic of me - sitting back in my easy chair, the mouse in one hand, the keyboard in the other, and my brain in an unspeakable place (smile). It sure is easy to lose my perspective... again, thank you.

Respectfully,
jund

[BlindSide]

Well, your needs certainly make more sense now; best of luck keeping that beast tame. And like I said before, it was just a misunderstanding; not worth those high words, but thanks anyway.