|
Sander Rossel wrote: When does the hurting stop?
When you stop using both dbms at the same time?
Or when you stop using them totally?
I never finish anyth
|
|
|
|
|
phil.o wrote: When you stop using both dbms at the same time?
Well, that may be a solution(if he wants stop getting hurt )
phil.o wrote: Or when you stop using them totally?
Don't tell me that you want him to us MS access
|
|
|
|
|
Brittle1618 wrote: Don't tell me that you want him to us MS access
No, I'm not so cruel
A simple Excel sheet will do it
I never finish anyth
|
|
|
|
|
|
I don't think so. At that time, extensive usage of both systems during your carreer will have caused severe brain damages, displacing the moral pain to a physical, unsustainable pain.
Better stick to Excel as early as possible
I never finish anyth
|
|
|
|
|
phil.o wrote: severe brain damages Causing you to miss the Reply button and hit Email instead?
phil.o wrote: Better stick to Excel as early as possible Better, I started in VB!
|
|
|
|
|
Sander Rossel wrote: Causing you to miss the Reply button and hit Email instead?
I wondered why I had to reply twice ^^ Now I know.
Sander Rossel wrote: Better, I started in VB!
Beware! VB is extremely dangerous. VB destroys ozone layer. VB causes cancer and other funny diseases.
I never finish anyth
|
|
|
|
|
BTW allready your subject does not work, it has to be "SQL <> SQL"
modified 19-Jan-21 21:04pm.
|
|
|
|
|
|
Works in SQL Server
PooperPig - Coming Soon
|
|
|
|
|
Sander Rossel wrote: When does the hurting stop
When you stop doing presentation logics in the database.
I also agree with Phil, why do you need to support more than one database?
|
|
|
|
|
Why? Layers are soooo last decade.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Our company uses Oracle and SQL Server, both from C#.
SQL Server support isn't really a requirement (now), but I was pretty sure it would work as it's SQL in it's simplest form (although apparently there is no 'simple' form of SQL)...
Anyway, screw SQL Server support.
|
|
|
|
|
It'll get even funnier when you realize that even when the SQL is completely compatible, the results may not be.
For example: Oracle doesn't have an empty string.
|
|
|
|
|
Jörgen Andersson wrote: For example: Oracle doesn't have an empty string. Or a bit/bool data type...
Jörgen Andersson wrote: It'll get even funnier I'm not laughing
|
|
|
|
|
Jörgen Andersson wrote: Oracle doesn't have
A GUID type.
In some databases a one-byte integer is signed; in others it's unsigned.
|
|
|
|
|
PIEBALDconsult wrote: A GUID type
Syntactic sugar. Use myguid RAW(16) default SYS_GUID()
Or rather, don't use them at all.
The only serious place where GUIDs have the edge over sequences is on distributed systems.
|
|
|
|
|
Jörgen Andersson wrote: is on distributed systems
They're all distributed systems.
|
|
|
|
|
Jörgen Andersson wrote: why do you need to support more than one database?
Because one features premium pay and the other features ubiquitous jobs?
|
|
|
|
|
If the minor differences between databases already make you cry, then please stay away from anything that has to do with browsers.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
CDP1802 wrote: stay away from anything that has to do with browsers As a full-stack web developer that'll be difficult.
And yes it makes me cry and gives me nightmares, why can't we all just get along?
Sometimes I want to go back to my safe and simple WinForms, now that's good technology
|
|
|
|
|
Very true, but some people think it just does not feel right if it is not as complicated and convoluted as possible. Browsers, CSS, JavaScript HTMl, throw them all away and build a native client where ever possible. Then you will certainly have a better UI.
As for the databases, perhaps you should use a ORM as abstraction. Then you can be fairly independent of the actual database that is used. At the price (as someone already noted) that you will do everybody a favor and not do any more presentation layer stuff in the data layer.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
CDP1802 wrote: perhaps you should use a ORM as abstraction This is the 'dynamic everything should be possible' kind of code. In my experience ORM's don't handle that very well... We've tried some solutions, but ultimately decided to build our own solution, which is what I'm now doing
CDP1802 wrote: you will do everybody a favor and not do any more presentation layer stuff in the data layer I'm not
|
|
|
|
|
Sander Rossel wrote: This is the 'dynamic everything should be possible' kind of code.
Good luck. Everybody and his dog must give it a try, I guess.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
CDP1802 wrote: perhaps you should use a ORM as abstraction
Works fine for CRUD, but...
|
|
|
|