"Orchid XP v7" <voi### [at] devnull> wrote in message
news:476457f1$1@news.povray.org...
> Darren New wrote:
>
> > Know something? The default is also to commit after every statement on
> > most DBs too. So? :-)
>
> Really? I've yet to see that...

How many database variations have you worked with? Oracle and ....

Post a reply to this message

"Orchid XP v7" <voi### [at] devnull> wrote in message
news:47645555$1@news.povray.org...
> Gilles Tran wrote:
>> Get some experience first.
>
> Right. And the 3 modules in database design I took during my degree...

University != experience.

You say that as if you're the only  person here who did database courses at
university. You're not.

Post a reply to this message

"Orchid XP v7" <voi### [at] devnull> wrote in message
news:47642e2a$1@news.povray.org...
>
> >> Why do you need to lock things to enforce transactional integrity?
> >> Locking is only one (suboptimal) way to solve the problem.
>
> That's only one way of implementing transactional integrity. (And, IMO,
> not a very good way.)

So, in your vast experience of databases, how would you do it?

Post a reply to this message

"andrel" <a_l### [at] hotmailcom> wrote in message
news:476### [at] hotmailcom...
> >
> There is a difference between stating that a program can not do
> something and asking the p.o-t for their opinion and experience. In
> practice the result here is the same, mainly because there are a lot of
> friendly people here that have com to know you over the years. IRL your
> mileage may vary. One of the main differences IRL is that the former
> tends shuts down all communication, while the latter invites the other
> to participate in an exchange of ideas.

And IRL, the former, if you are wrong, can do sufficinet damage to your
reputation that it takes months or longer to recover. Especially if you are
in a position where your word is trusted

Post a reply to this message

47645555$1@news.povray.org...

> Right. And the 3 modules in database design I took during my degree 
> looking at different transaction isolation levevls and so forth was 
> probably balony too - along with the 3 A* grades I got for those modules.

So why are you asking newbie questions about ODBC and keep having these 
far-out opinions about things you are visibly ignorant about? Why can't you 
find the information by yourself? How much difficult it is to actually look 
up the MySQL (or Word, or whatever software or thing baffles you) manual to 
verify your claims? How difficult it is to actually listen to what 
professionals like Darren and Tom and Gail are telling you? I told you 
before: be ignorant is all right, being and acting clueless much less so. If 
you want to be taken seriously (and expect more than snarky replies in the 
future), don't act like a 15-year old script kiddie.

G.

Post a reply to this message

Gail Shaw wrote:
> 
> Actually Darren wrote that, but thanks for the vote of confidence.
> 
> Given a choice, I'd listn to Darren who's worked extensivle (from what he
> says) with MySQL. Personally I'm a SQL Server fan.
> 
> 

You and Darren have both given him good advice.  The quoted portion is 
just myself and Andrew, though this thread has grown a few similar branches.

Post a reply to this message

Orchid XP v7 wrote:
> Really? I've yet to see that...

BTW, GIYF. Google for "autocommit" and the name of your database of 
choice. It's really *easy*, ya know. :-)

-- 
   Darren New / San Diego, CA, USA (PST)
     It's not feature creep if you put it
     at the end and adjust the release date.

Post a reply to this message

Gail Shaw wrote:
> Actually Darren wrote that, but thanks for the vote of confidence.

I'm not sure what I wrote, but I don't think it was anything there 
quoted. :-)

> Given a choice, I'd listn to Darren who's worked extensivle (from what he
> says) with MySQL. Personally I'm a SQL Server fan.

I've done a bunch of SQL Server, too. MySql for Linux, SQL Server for 
Windows. Depends on the technology talking to the server. I tend not to 
use a lot of the fancy stuff that isn't particularly portable (enforcing 
privs in the database, returning multiple tables from a query, etc), and 
I don't tend to do a whole lot of DBA infrastructure things myself (like 
setting up hot fall-over spares etc).

-- 
   Darren New / San Diego, CA, USA (PST)
     It's not feature creep if you put it
     at the end and adjust the release date.

Post a reply to this message

Darren New wrote:

> It's really *easy*, ya know. :-)
> 

Not if you are googlephobic!

Post a reply to this message

"Darren New" <dne### [at] sanrrcom> wrote in message
news:476564ca$1@news.povray.org...
> Gail Shaw wrote:
> > Actually Darren wrote that, but thanks for the vote of confidence.
>
> I'm not sure what I wrote, but I don't think it was anything there
> quoted. :-)

Thread go so branched, I couldn't work out who said what and where. I knew I
didn't say it though.

> I've done a bunch of SQL Server, too. MySql for Linux, SQL Server for
> Windows. Depends on the technology talking to the server. I tend not to
> use a lot of the fancy stuff that isn't particularly portable (enforcing
> privs in the database, returning multiple tables from a query, etc),

My stuff (fortunatly) doesn't need to be portable, so I can go as fansy as I
like.

> and
> I don't tend to do a whole lot of DBA infrastructure things myself (like
> setting up hot fall-over spares etc).

Me neither. *shudder* I joke that if asked to backup a database, I'd have to
check the manual for the syntax. I'm more a developer that specialises in
performance tuning. Is fun, most days

Post a reply to this message