followed tags: 19
followed domains: 0
badges given: 0 of 0
member for: 1535 days
Thanks! I'm really interested in a bunch of the other api's they offer to interact with watson.
- I'm running the Windows 10 Insider Preview
That fact kind of invalidates his whole testing regime.
Unless he goes back and tests on release of the OS and his results are the same.
I can't wait to see how you finalize your approach. I have one co-worker nodding his head violently at the prospect that business logic should be handled by the application and enhanced by interfaces as needed while another swears by handling everything in the db.
I lean toward the latter; but I know nothing.
Thanks for the updates, man. Godspeed.
I wish there were two of you so one could keep an adequate log of all the shit you have to do throughout your conversion process. I'm sad to have missed your livestream.
Enhancing the performance of your queries is a lot of guesswork without the right tools. I need to hop in feet first in some PostgreSQL but that sweet Cassandra is calling my name.
Does the Arc SQL adapter support the use of stored procedures? Have you tried wrapping a view around one of the bulkier tables to filter the results a little and maybe weed out some unnecessary/problem columns? Is your dataset normalized?
I know a bunch of questions isn't going to help; but holy snark I love me some DB discussion.
I guess those questions are the 'urgent' ones.
My "urgent" questions are more along the following:
"Touching back on the EULA, why must I accept automated updates? I personally have an environment in which stability is key and automated updating has burned me in the past...just kidding, six days ago.
- Updates. The software periodically checks for system and app updates, and downloads and installs them for you. You may obtain updates only from Microsoft or authorized sources, and Microsoft may need to update your system to provide you with those updates. By accepting this agreement, you agree to receive these types of automatic updates without any additional notice.
Did I mention scary?
Haha, I'd call you a blasphemer! Let the application generate the Id?! What kind of voodoo are you throwing out here?! (jk)
I'm slowly finding my love for software development residing within the confines of database work.
Most of our legacy application code is generally stable and a lot of tasks I find myself doing is data migration and query optimization. Before that there was a ton of handwritten replication (don't ever do it, please; but if you have to give me a call) but thats all out the window with an in-house automated solution. Almost all my coworkers are database enthusiasts, a few of which I would call fanatics. A couple posses a lifetime of wisdom within the subject that has left me really inspired.
I'm super stoked about you throwing up the schema, thanks a lot!
It might not be a terrible idea to auto increment a primary key on those reference tables for whenever they get big. You'd just put a FK constraint on those one-to-many relationships in the other tables.
create table if not exists "publication_shared_by" (
id integer identity(1,1), --primary key will help when this table becomes large publication_id integer, -- fk into publication, NOT a pk, one to many username text --create a non-clustered index to the 'username' table or something
I'm not sure if the identity(1,1) syntax is correct (I work primarily with a T-SQL system).