多用户方法

编程入门 行业动态 更新时间:2024-10-13 08:24:46
本文介绍了多用户方法的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧! 问题描述

请问。假设在销售订单数据条目中,我是否必须保存空白SO或取消它?我是否必须立即创建SO号码或仅在保存SO时创建一个号码?我的SO号码不是我的主键。我有一个主键设置为在sql server上自动增量。 感谢。

Idea please. Suppose in a Sales Order data entry, do i have to save the blank SO or cancel it? Do i have to create right away an SO number or create a number only when saving SO? My SO number is not my primary key. I have a primary key set to autoincrement on sql server.thanks.

推荐答案

嗯,你需要提供更多为了得到你问题的明确答案,背景说 - 保存空白的销售订单除了浪费数据库空间之外没有任何其他用途,除非你打算对以前开始的销售订单记录进行某种恢复......我个人认为取消它并且根本不将记录写入您的数据库。至于立即创建销售订单编号,这取决于您从上一个问题做出的决定。在接受我之前的回答时,您需要在保存时创建它 - 如果此人取消订单或出现错误,您创建了一个不需要它的销售订单号,从而搞砸了任何保留的希望数据库中的一组连续记录。 在旁注中 - 您可能想重新考虑使用自动编号作为主键,它可以根据您的数据量身定制索引的任何收益......只是值得深思。希望这有帮助,左Aj Well, you'd need to provide a ton more background to get a definitive answer to your questions, that said - Saving a blank sales order doesn't serve any purpose other than to waste space in your database unless you plan to do some sort of recovery of previously started sales order records...personally I'd assume to cancel it and simply not write the record to your database.  As for creating a sales order number immediately, that depends on the decision you make from the previous question.  In taking with my previous answer, you'd want to create it on save - if the person cancels an order or there is an error, you've created a sales order number with no need for it and thus screwed up any hope of keeping a sequential set of records in your database.  On a side note - you might want to reconsider using an AutoNumber for your primary key, it sorta kills any gains in terms of indexing being tailored to your data...just food for thought. Hope this helps, Aj

更多推荐

多用户方法

本文发布于:2023-10-24 21:05:23,感谢您对本站的认可!
本文链接:https://www.elefans.com/category/jswz/34/1525001.html
版权声明:本站内容均来自互联网,仅供演示用,请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系,我们将在24小时内删除。
本文标签:多用户   方法

发布评论

评论列表 (有 0 条评论)
草根站长

>www.elefans.com

编程频道|电子爱好者 - 技术资讯及电子产品介绍!