Azure Easy Tables 是否支持关系? [英] Do Azure Easy Tables support relationships?

问题描述

我刚刚在学习 Azure 移动应用.Easy Tables 支持关系吗?我现有的架构有多个带有外键约束的表，我需要能够创建复杂的连接(Easy APIs).我试图理解所有这些简单"的东西的意义.

I'm just learning about Azure Mobile Apps. Do Easy Tables support relationships? My existing schema has multiple tables with foreign key constraints, and I need the ability to create complex joins (Easy APIs). I'm trying to understand the point of all this "Easy" stuff.

我应该跳过它而只创建一个自定义的 ApiController 和手动数据库脚本部署吗?

Should I skip it and just create a custom ApiController and manual db script deployment?

推荐答案

Easy Tables 只是通过 Web API OData 服务端点公开的简单 SQL Azure 表.因此，当您创建它们时，您可以连接到 SQL Azure 并在那里创建您的关系等，并自定义 API 代码以在响应中包含这些关系数据.

Easy Tables are just simple SQL Azure tables that are exposed through a Web API OData Service endpoint. So when you create them you can connect to the SQL Azure and create your relationships etc there and customize the API code to include those relational data in the response.

根据我的经验，如果您没有复杂的逻辑/业务规则或复杂的查询，它们会很好.

From my experience they are good if you dont have complicated logic/business rules or complicated queries.

根据我的经验，如果您有复杂的东西，即使是普通的 Web API OData 服务端点也无济于事，因为请求的拦截会使代码变得复杂，您最好创建自己的 Web API.

To my experience if you have complicated stuff even normal Web API OData Service endpoints would not help because the interception of the requests makes the code complicated and you are better off creating your own Web APIs.

我几乎觉得 Easy API 和 Easy Tables 的设计目的是让您在黑客马拉松中为一个简单的移动应用程序提供一个快速的开始，或者将一个想法放在一起作为演示真正快速.但是对于现实生活中的企业内容，我将构建自己的 Web API.

I almost feel like the Easy API and Easy Tables are more designed to give you a kick start for a simple mobile app in a hackathon or to put an idea together as a demo real quick. But for real life enterprise stuff I will go with building my own Web API.

这篇关于Azure Easy Tables 是否支持关系?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！